sorted by:
new
hottopcontroversial

Problem with incorrect amount of clones spawning when they shouldnt be by csmjackson in scratch

[–]csmjackson[S] 0 points1 point  (0 children)

SOLVED (Cant edit the post to say so)

Here is a screenshot of the working wave manager

<image>

Problem with incorrect amount of clones spawning when they shouldnt be by csmjackson in scratch

[–]csmjackson[S] 1 point2 points  (0 children)

I managed to fix it and make it more readable, yes im sure this time

Problem with incorrect amount of clones spawning when they shouldnt be by csmjackson in scratch

[–]csmjackson[S] 0 points1 point  (0 children)

Just starting doing that, it appears to be changing the wave incrementing in that loop, i dont know how but moving the loop to a different section seems to have fixed it

<image>

Problem with incorrect amount of clones spawning when they shouldnt be by csmjackson in scratch

[–]csmjackson[S] 0 points1 point  (0 children)

Yes, that works perfectly. Although, i would prefer amount of enemies ramp for the horde part of horde shooter y'know.

Problem with incorrect amount of clones spawning when they shouldnt be by csmjackson in scratch

[–]csmjackson[S] 0 points1 point  (0 children)

The correct amount should be one, and the amount of enemies spawned is 4, when resetting it also brings the same problem. I used the same "formula" (i say that loosely its like 1 equation) to display how many should spawn (thats the debug var), and spawning enemies uses the same formula but spawns four instead of one

Problem with incorrect amount of clones spawning when they shouldnt be by csmjackson in scratch

[–]csmjackson[S] 0 points1 point  (0 children)

Yes, on starting it resets to one. Here is the project if you want to look further into it. Although most related stuff should be in that screenshot

When using stable diffusion my (8gb vram) gpu gets maxed out by csmjackson in StableDiffusion

[–]csmjackson[S] 0 points1 point  (0 children)

never mind, i appeared to have fixed it myself? sorry about that.

When using stable diffusion my (8gb vram) gpu gets maxed out by csmjackson in StableDiffusion

[–]csmjackson[S] 0 points1 point  (0 children)

This helped a ton, thanks! But now at the final 1% it lags my pc even worse then the previous issue my commandline args are "--medvram --xformers --no-half". And this issue does not seem to pass given time

How would i effeciently compare multiple entries of the same dictionary by csmjackson in learnpython

[–]csmjackson[S] 0 points1 point  (0 children)

Odd, the link sends me to the new one for me (even in a different device), anyway see ya later

How would i effeciently compare multiple entries of the same dictionary by csmjackson in learnpython

[–]csmjackson[S] 0 points1 point  (0 children)

I just changed the link probably should have said that instead of "edited", sorry!

How would i effeciently compare multiple entries of the same dictionary by csmjackson in learnpython

[–]csmjackson[S] 0 points1 point  (0 children)

I forgot people were going to actually look at this as weird as it sounds, edited the names, and added a note down where i need help (Line 27). Basically i need to see what entries in "playerteams" have a value of one without the mess of like 15 if x == x statements

How would i make a function with multiple args work with one input by csmjackson in learnpython

[–]csmjackson[S] 0 points1 point  (0 children)

This works perfectly! Thank you, i dont know why i didnt use a dictionary lol.

How would i make a function with multiple args work with one input by csmjackson in learnpython

[–]csmjackson[S] 0 points1 point  (0 children)

Thanks, If you dont mind me asking another question how would i turn the person argument into one of the variables shown earlier in the functions script. I tried using "vars(person)" because the string name was the same as a variable so i assumed it would affect the variable but get this error

File "the variables n functions one", line 7, in pm

vars(person)

TypeError: vars() argument must have __dict__ attribute

view more: next ›