ZDoom 2.1.7

HotWax · Post by **HotWax** » Tue Oct 31, 2006 3:30 pm

I'm guessing this is how it works:

TNT1 A 0 A_Jump(255, 4, 6, 8, 12, 16)

Always jumps, and has an equal chance of jumping ahead 4, 6, 8, 12, or 16 frames.

Post by **Graf Zahl** » Tue Oct 31, 2006 3:33 pm

256 jumps always.
255 still has a small chance that it won't jump at all.

Post by **Nash** » Tue Oct 31, 2006 3:35 pm

Alright, thanks.

I assumed A_Jump(128, random(1,50)) though...

Unknown_Assassin · Post by **Unknown_Assassin** » Tue Oct 31, 2006 5:12 pm

YAY! I'll download it, when I get home.

Now we just wait for the arrival of ZHalloween.

Kaiser · Post by **Kaiser** » Tue Oct 31, 2006 5:55 pm

Okay, why is zdoom now crashing my maps/scripts with divide by zero errors while the older versions past 2.1.1 never did this at all?

Lemonzest · Post by **Lemonzest** » Tue Oct 31, 2006 6:29 pm

Demo's work as they should, as does the OS detection

HotWax · Post by **HotWax** » Tue Oct 31, 2006 6:55 pm

Kaiser wrote:Okay, why is zdoom now crashing my maps/scripts with divide by zero errors while the older versions past 2.1.1 never did this at all?

Post the offending script?

Anakin S. · Post by **Anakin S.** » Tue Oct 31, 2006 7:02 pm

HotWax wrote:I'm guessing this is how it works:
Code: Select all
TNT1 A 0 A_Jump(255, 4, 6, 8, 12, 16)
Always jumps, and has an equal chance of jumping ahead 4, 6, 8, 12, or 16 frames.

So does A_Jump(64, 4, 6, 8, 12, 16) mean that it has 1/4 chance of jumping 4, 6, 8, 12, 16 frames?

HotWax · Post by **HotWax** » Tue Oct 31, 2006 7:04 pm

Anakin S. wrote:So does A_Jump(64, 4, 6, 8, 12, 16) mean that it has 1/4 chance of jumping 4, 6, 8, 12, 16 frames?

It means it has roughly a 1 in 4 (25%) chance to jump, and if it does decide to jump, it has an even chance of jumping to 4, 6, 8, 12, or 16 frames. (In this case, 20% chance each) If it doesn't jump (the other 75% of the time), it proceeds to the next frame in sequence as normal.

Kaiser · Post by **Kaiser** » Tue Oct 31, 2006 7:26 pm

HotWax wrote: Post the offending script?

No

It turns out its not the script nor decorate. But the map(s) itself. I already deleted all behaviors and decorate lump and its still crashing with a int divide by zero error.

Anakin S. · Post by **Anakin S.** » Tue Oct 31, 2006 7:36 pm

HotWax wrote:
Anakin S. wrote:So does A_Jump(64, 4, 6, 8, 12, 16) mean that it has 1/4 chance of jumping 4, 6, 8, 12, 16 frames?
It means it has roughly a 1 in 4 (25%) chance to jump, and if it does decide to jump, it has an even chance of jumping to 4, 6, 8, 12, or 16 frames. (In this case, 20% chance each) If it doesn't jump (the other 75% of the time), it proceeds to the next frame in sequence as normal.

Okay. That makes sense. Thanks.

HotWax · Post by **HotWax** » Tue Oct 31, 2006 7:39 pm

Kaiser wrote:Command line: E:\DOOM2\ZDOOM.EXE -warp 6 -file E:\Doom2\deepsea\Work\KA2379~1.WAD E:\Doom2\deepsea\Work\K21_RE~1.WAD -skill 4 -nomonsters -iwad E:\Doom2\zdoom2.wad

There's your problem!

I kid, I kid.......

Post by **Graf Zahl** » Wed Nov 01, 2006 1:07 am

Still, without the map there's not much of a chance to find what's wrong.

Hirogen2 · Post by **Hirogen2** » Wed Nov 01, 2006 1:51 am

Graf Zahl wrote:
TheDarkArchon wrote:It's mostly developer side that it would benefit. Also, if I'm not mistaken, it would help prevent some of the errors caused by fixed point math such as rendering artifacts.
Not to mention that it introduces other inaccuracies. I wonder whether it is worth the danger of network desyncs. Remember, Randy fixed such an error for 2.1.7.

Try and see. To note: I have an accuracy problem in GL mode (so I doubt it has to do with the fixed math). In dark rooms, one can see a white pixel where [GL] vertexes are, you can especially notice it in P:AR, which has a lot of vertices. Or maybe it is just that my card is a little dated (NV11).

Post by **NiGHTMARE** » Wed Nov 01, 2006 7:22 am

Hirogen2 wrote:Try and see. To note: I have an accuracy problem in GL mode (so I doubt it has to do with the fixed math). In dark rooms, one can see a white pixel where [GL] vertexes are, you can especially notice it in P:AR, which has a lot of vertices. Or maybe it is just that my card is a little dated (NV11).

Do you have rendering quality set to quality, or to speed? If the latter, try switching to the former.