Digital Earthworks track export stalling

[kidzorro]

Hey guys,

My .track export is stalling without showing any error messages. The issue is similar to that of a previous thread http://twisteddirt.com/smf/index.php?topic=4535.0
The track compiles normally, and all custom object libraries are functional, however after exporting there's just one file (Beta_Sx_Track_Slot_1.dx9.scene) to be found in the database folder. I thought it may have something to do with there being too many custom objects in the DE project. So I tried removing several custom objects one by one and was able to export the track at one point. However, as I started adding more objects the export would stall again at random. Made sure all my Windows 8 security permissions are in check for the database folder and DE executable file, so that shouldn't be the issue.
and now I'm out of ideas.

Any help on this would really be appreciated. Thanks!

Here's the log    https://www.dropbox.com/s/uza6hhuyu8fu18z/Logging%20Track%20Loading.txt?dl=0

[mcm2boys]

Sounds like it might be a memory thing, or too many objects for DE to hold in memory. How many objects have you got in there and is it a nat or sx?

[kidzorro]

Thanks for the quick response!

It's an sx track. I have 564 objects in the project, however in previous instances I've had up to 590 objects without export problems.

Regarding the objects, most are custom objects and they are elements of a stadium. I have been optimizing the geometry of each element in order to make it easier to bake textures for them. So in other words the current version of my .track file is less complex than previous instances. Previously it was not a problem at all having many objects in the scene. But a few days ago the export started stalling at random, sometimes it would work and sometimes it would fail even with the same objects in the scene. When the export failed I would reboot my system and get it exporting again and so on.

So I'm a bit divided as to whether the problem is the objects themselves. Could it have anything to do with Windows updates?

Anyway I'm back to removing one object at a time. The export works with some objects, others not. The objects that are causing the export stall, are not very detailed however large in scale (stadium walls and bleachers etc). I really hope that there is way to get around this problem, since I'm so close to completing the track.

If you have any other ideas I would appreciate it a lot. Thanks!

[Darkslides19]

I dont really remember but i think monster704 (Lake Valley) had the same problem.. i think he fixed it with soemthing giving DE more RAM or something.. i'd talk to him

[kidzorro]

Update - I tried grouping several custom objects in DE before exporting, which worked twice, as I added more objects the export stalled again. I also lowered the texture resolution on complex custom objects, didn't make a difference.

Anyway, messaged monster704. Hopefully there's a way around the memory limitation in DE. thanks man

[mcm2boys]

DE limits memory to 2GB since it's a 32bit application. Monster74 found a program online that can change the memory that an application uses to 4gb which worked for him, since DE just ran out of memory.

I'm working on some fixes including increasing the memory allocation to 4gb and hopefully down the line a 64bit version. If you're problem is memory then Monster74's fix will help. Here's a link to the program he used. http://www.ntcore.com/4gb_patch.php

[kidzorro]

Monster64's fix worked! Thanks guys for all the help as always

[Darkslides19]

That's what i was talking about

[mcm2boys]

Yeah i know, that's what reminded me that Monster74 gave me the link..