kdau on 9/7/2013 at 09:40
Quote Posted by fibanocci
Thanks. Looks like, it's working now. I can read the signs. Got a crash when I used the switch under the effects (weather) sign. Everything else seems to work properly.
Quote Posted by Firehawk
I got the same crash with the new Version. With the old Version everthing works fine for me
Hmm. Unfortunately, there are about 20 things that happen when that switch is frobbed, and it could be any of them. Was there anything interesting written to the monolog right before the crash? Or any backtrace/other crash info in the Windows crash dialog?
On the other hand, if the crash wasn't happening with 0.1.0.1, it's probably because I went back to cross-compiling for 0.1.1. If that's the problem, I'll have to go borrow the Windows computer and compile it there every time I need to release this thing. :erg:
fibanocci on 9/7/2013 at 10:58
I guess, the crash didn't happen before, since kdscript wasn't loaded at all?
Windows tells me about a problem in ntdll.dll
offset 00029f07
Pure vital function call R6025
Monologs last words before crashing:
KDCarrier [138]: attaching SmokingPipe (-6785) to joint 2
Failed to load palette intrface\synch
R Soul on 9/7/2013 at 11:18
I'm getting the crash with the 'effects' switch too. It's caused by KDTrapWeather. The Fog and EnvMap scripts work fine.
The other scripts in the demo work as described.
Apiai on 9/7/2013 at 17:52
Congratulation, this is a really nice demo, the possibilities seem awesome !
It works for me at first attempt : windows 7, NewDark 1.21
Sliptip on 9/7/2013 at 22:04
Just tried the latest version (version 0.1.1) and found the same as the other WinXp users. Everything works great except for a crash with the effects switch.
I really look forward to experimenting with these! :D
R Soul on 9/7/2013 at 23:49
Imagine a sudden downpour and lots of AI deciding to find shelter till it passes. A thief might just have a chance to get through a guarded door.
kdau on 10/7/2013 at 18:36
Hello all. <del>Based on my research into the R6025 crash ("Effects" switch), I think it's a NewDark bug specific to Windows XP. A few people have reported it with other recent FMs, but it was less consistent than here. I'm going to PM each of you getting crashes with some follow-up questions, to keep from overloading this thread.</del> <ins>This was wrong; see below.</ins>
Meanwhile I've been working on a new version that adds or fixes some minor features and progresses toward T1/TG compatibility. For those of you who have been able to run the entire demo and/or look at the documentation, is there anything about the scripts so far that you would like to see changed? Inconvenient usage, missing options, limitations, etc.?
kdau on 10/7/2013 at 20:04
Well, I somehow managed to reproduce the bug myself on Win7, so <del>I've been able to fix it</del> <ins>I'm making progress on fixing it</ins>. Version 0.3.0, including that fix and various small new features, should be ready <del>later today (GMT-7).</del> <ins>soon. (I'd gotten it to work, but now it's crashing again. Further investigation tomorrow.)</ins>
fibanocci, your R6025 crash was for a related but different reason. I'll PM you details.
Vae on 11/7/2013 at 00:15
Thank you kindly, kdau...I love the possibilities...:)
Sliptip on 11/7/2013 at 02:28
Question about KDToolSight
I'm using a default tool sight on the CustomHUD object. I decided to change the tool sight for one of my projectiles, however the projectile has other projectiles that inherit from it. I notice they don't inherit the tool sight image from the parent, but rather from the CustomHUD. Would it be possible to change that? It's a really minor (and easily circumventable) thing but it felt kind of "off" from the way most things inherit in Dromed.
Do you think it would be possible in the future to offset the tool sight graphic?
