BlazingPhoenix
AAAAAAAAAAAAA
YES! thankyouthankyouthankyou. :D
*praises the programmer*
*praises the programmer*
This happened when testing a wad (Clicking on that green button) in the newest version.Runtype Error 53:
Type mismatch
KingofFlames said:AHHHHHHHHH, the bug isn't fixed! :( :( :(
*flees from mapping until EVERY bug is fixed*
Tapika the fox said:This happened when testing a wad (Clicking on that green button) in the newest version.Runtype Error 53:
Type mismatch
Also, this isn't really a glitch, but it should be called SRBBuilder.
I edited my earlier post while you were posting -- does that fix it?Tapika said:It happens with any wad (I tested all the ones I have) that was created before this build.
Oogaland said:Could you set the executable in the Testing options to this EXE, please, and post what it says when you try testing? It'll echo the arguments passed to it on the command line. There're one or two other things wrong with testing, so I'll release a quick patch later today, assuming I can get to the bottom of this one.JJames19119 said:EDIT2: Okay, I just tried testing out and no matter what parameters I feed it, it makes SRB2 come up with a weird "P_InitPicAnims: bad cycle from AFALL1 to AFALL2" error, making testing impossible...
Ah, okay. I've always just let it get tex previews from the IWAD and been content to have an "Unknown Flat" for F_SKY1, which is why I hadn't picked up on this earlier. I'll add a checkbox to the testing options to determine whether the resources wad should be included. I still plan to get a small update out within the next few hours.JJames19119 said:I see what's wrong. It's trying to include the "gfx.wad" file I always make DB use so I can see the texture previews and use F_SKY as a texture. (DB can't list the texture pictures from srb2.srb alone and F_SKY is never listed at all) Of course, it shouldn't normally be including gfx.wad...
EDIT: Nevermind, it appears that with a bit of work, it can list the texture pictures quite fine but still makes F_SKY an unknown flat..
And KoF: I've tried so very hard to reproduce the bug the same exact way I did before but to me, the bug has been fixed.
Good to know, I hope you find out what's causing the problem.Oogaland said:No progress on your bug yet, KoF, although I'd hope it'll be fairly straightforward to fix once I can reproduce it. (And I notice I missed you on IRC again... Maybe next time...) Expect an r19 once that's been seen to, after which normal proceedings should resume.
Tapika the fox said:Do-do while trying to put the latest build on my hard drive.
[Excessive Images]