L3DT users' community
Large 3D terrain generator

A very bad bug in Sapphire [Fixed?]

Please report software faults here.

A very bad bug in Sapphire [Fixed?]

Postby Exi » Mon Oct 18, 2010 10:01 pm

Hi, I just recently bought a new computer, and I was running L3DT Pro 2.9 on it for a while. Then, one day, when I opened up Sapphire, it bugged out. It would open a new screen, like normal, then there would be an error. I don't know how to post images, but the error said that the function "ExtShowWnd" had failed. What is up with this? Does it have something to do with the size of my terrain (51200x51200 with 25x25 mosaic tiles), because Sapphire works fine for those. I am on a schedule, and I need a fix in a bad way! Thanks!
-Exi[/img]
Exi
New member
 
Posts: 7
Joined: Mon Oct 18, 2010 2:40 am

Postby Exi » Tue Oct 19, 2010 12:41 am

My bad, I meant to say that Sapphire works fine for terrains smaller than that (51200x51200). Sorry.
Exi
New member
 
Posts: 7
Joined: Mon Oct 18, 2010 2:40 am

Postby Aaron » Tue Oct 19, 2010 9:07 pm

Hi Exi,

Thanks for the bug report. My guess is that Sapphire is running out of memory when loading the map geometry (this happens in the ExtShowWnd). It is therefore probably due to the map size. I'll put the fix for this on the dev plan for the next release. I apologise for this inconvenience.

Best regards,
Aaron.
User avatar
Aaron
Site Admin
 
Posts: 3696
Joined: Sun Nov 20, 2005 2:41 pm
Location: Melbourne, Australia

Postby Exi » Tue Oct 19, 2010 9:24 pm

Okay, is there an ETA for the next release?
Exi
New member
 
Posts: 7
Joined: Mon Oct 18, 2010 2:40 am

Postby Aaron » Wed Oct 20, 2010 10:04 pm

Hi Exi,

Sorry, I don't have a firm ETA yet for the release of v3.0, other than to say sometime early to mid next year. Many substantial changes have been made in the next version, including a new plugin API, a 64-bit version, and changes to memory allocation of maps (e.g. use of system pagefile by default). These changes will take a while to bed down and debug, so I can't see a stable release being ready in the next few months.

However, a 'fixed' Sapphire may be included with a developmental build prior to the final release of v3.0. I'll post back here when it's available.

Best regards,
Aaron.
User avatar
Aaron
Site Admin
 
Posts: 3696
Joined: Sun Nov 20, 2005 2:41 pm
Location: Melbourne, Australia

Postby Exi » Fri Oct 22, 2010 9:38 pm

Thank you very much!
Exi
New member
 
Posts: 7
Joined: Mon Oct 18, 2010 2:40 am

Re: A very bad bug

Postby Exi » Sun Feb 06, 2011 3:00 pm

New developments in my project, and I now really need the epicness of L3DT. Any new updates on a fix?
Exi
New member
 
Posts: 7
Joined: Mon Oct 18, 2010 2:40 am

Re: A very bad bug

Postby Aaron » Wed Mar 16, 2011 10:07 pm

Hi Exi,

Sorry, this is still on the dev plan for v3.0, but I've not made much progress yet. I will post back here when something is available.

Best regards,
Aaron.
User avatar
Aaron
Site Admin
 
Posts: 3696
Joined: Sun Nov 20, 2005 2:41 pm
Location: Melbourne, Australia

Re: A very bad bug

Postby Exi » Wed Mar 16, 2011 11:38 pm

Great, thanks. Take your time, I am sure 3.0 will be epic ;)
Exi
New member
 
Posts: 7
Joined: Mon Oct 18, 2010 2:40 am

Re: A very bad bug

Postby Aaron » Fri Mar 23, 2012 1:21 pm

Hi Exi,

I apologise for the delay in resolving this problem. This bug has now been fixed in L3DT Professional v12.03 build 2 (blog here), which is on the downloads page now. Please let me know if you find any problems with this version, or if you would like to make suggestions for further changes. Thank you again for the bug report, and for your considerable patience.

Best regards,
Aaron.
User avatar
Aaron
Site Admin
 
Posts: 3696
Joined: Sun Nov 20, 2005 2:41 pm
Location: Melbourne, Australia


Return to Bug reports

Who is online

Users browsing this forum: No registered users and 7 guests

cron