DeleD Community Edition

[z80]

Hi
I've got an error using deledlite 1.1

"TScene.Load:TScene.Load110:Access violation at address 0040419A in module "Deled.exe" Read of address 02D8E070"

I cannot open my project now.
Is it limitation for deledlite ??
Thanks

Win98SE, Ram 384Mb DDR, Geforce3

[Paul-Jan]

Hi Z80 (cool name by the way), welcome to these forums!

To answer your question: no, there are definitely no such limitations in DeleD Lite, what you have stumbled upon is a bug (and a serious one at that!). Could you send me the dmf (and, if you used custom textures and it isn't too much work, the textures too) so that I can take a look at it and see if I can fix both the bug in DeleD and, if possible, recover your project? My e-mail adress is paul [at] delgine [dot] com. Thanks!

Did you do anything special last time you were working on this project? I know it may be hard to remember, but this issue is quite serious, and any hints on how this occured may help.

[Paul-Jan]

(posting this to both the forum and e-mail)

Hi Z80,

Thanks for your e-mail. I really like the 'semi-cartoony' game style!

I started with level73.dmf. As far as I can see, there is nothing wrong with it: I loaded it into DeleD 1.1 Lite, added some grass textures, drew some rectangles with it, added some cubes, saved it to test.dmf, loaded it... works just fine. Did some more fiddling around: things just kept on working.

This means that whatever happened on your computer, was due to some local circumstances: either the exact actions you performed, or maybe (less likely) some limitations on your computer (gfx card out of texture memory, hardisk full, out of memory).

Too bad you can't remember the exact error you got, it might have given us some clues in reproducing the problem. As it is now, I simply can't figure out how to reproduce your problem on my computer, so I can't really do much to fix it. Any extra info you might have on how to make it 'crash' on my machine would be most welcome!

Now on to level74.dmf, when debugging I can see the underlying problem here is a 'NAN is not a floating point value' bug. Which is interesting, because that is reported by LEGIT (http://www.delgine.com/forum/viewtopic.php?t=500) as well.

If you open it up in notepad (.dmf files are simple text files exactly for this purpose), and search for NAN, you will find that for some reason the four vertices of rectangle280 all have NAN texture coordinates (NAN means 'not a number', usually a division by zero result or something similar). Any chance of remembering where rectangle280 was located, and what could have gone wrong?

If you want to fix things, do the following:
1. Open up texture74.dmf in notepad
2. Replace NAN by 0 (8 occurances)
3. Open up Level74.dmf in DeleD (this will now work fine)
4. Open up the Scene Inspector
5. Select rectangle280 (near the bottom)
6. Hit [delete] and confirm.
7. Save the dmf file

For your convenience I have included level75.dmf with the e-mail, which is simply level74.dmf with the above steps applied.

So the best thing to do now is to continue your work with this level. Keep a sharp eye open: if something goes wrong, please write down the error message and try to recall what you were doing. We really want to fix this bug, but we need some help...

Thanks!
- PJ -

[Paul-Jan]

By the way, the fact that DeleD reports an Access Violation instead of the correct errormessage is a bug in it's own, I have put it on the list and it will be fixed asap.

[update: fixed (in the next DeleD update)]

[Dl187]

I have encountered a similar problem, First I export in .X then I tried loading it in Giles, it loaded fine but when I exported it as Dbo (Which has worked prior to the problem) said Memory Access Violation and crashed although i found a way around this by re exporting it as .X in giles I would rather export as .DBO without it crashing. I have also tried the x file in Darkbasic Pro but it also crashed.

This is when the problem began. First I imported several .OBJ files into Deled lite 1.0 (Which has worked before) then I thought that I should remove and reload 2 of the textures that never showed when I exported so I did and then I tried exporting as .X and thats when the errors came about. It doesnt say anything in deled though.

[Jeroen]

[Dl187]

Well the x file does not load in Darkbasic pro either. I mean I use to be able to load it into Darkbasic pro right after I exported it but ever since the problem I havent been able too. I even tried to take away existing models that I recently added and tried to take it back to the state of when it use to work fine but it ends up crashing both programs still.


Btw Thanks for Replying

[Paul-Jan]

So the problem boils down to a .X file that crashes when you load it into Darkbasic Pro. However, the .X file loads perfectly into Gile[s] (so there is nothing wrong with the .X file itself), and when you convert it into a DBO with Gile[s] it still crashes Darkbasic Pro. To me, it seems most likely here that the real problem is some incompatability in Darkbasic Pro

So the question is, what aspect of that scene does Darkbasic not like. For us, that is really hard to figure out, as we don't have Darkbasic Pro, but what you can do is simply load the .X file into notepad, cut out bits and pieces, until things work again. My first bet would be some texture that is in a format Darkbasic Pro doesn't recognize.

If everything else fails, and the files are not too big, you could try sending the .X (and/or the .DMF) including textures to me (paul [at] delgine [dot] com), and I could try to give it a spin.

[Dl187]

Hey

Well I seem to have found another work around that works perfectly but requires me to merge the scene in deled before exporting, now it works in .X format as well as .Dbo I wounder what it could of been. Anyways if you would like me to send you the dmf file i could do so.


*I sent you the file*

[Paul-Jan]

Ah, good to know merging solves the problem. Thanks for the file, I will give it a try!