L3DT users' community
Large 3D terrain generator

strange message when rendering 24x48 to texture with 2xratio

Please report software faults here.

strange message when rendering 24x48 to texture with 2xratio

Postby silent303 » Sun Mar 04, 2007 9:31 pm

hi there,

today i tried to render my first time texture map with 24x48 size to texture, and always there comes this message when i set ratio over 1 in texture map. the other maps (atributes, light etc.) run well with 4xratio.
also had no problems with a 16x16 map and 4xratio, even 8xratio went well before.


message: (the error apears when the texture render (in preview) hit the right side and want to render the "half block"
(in dual thread, the upper render starts until the half block again and gives second error message)

Log cleared
zoefunc_calc_TX_area_pro error
- cannot get attributes map pixel

CMapWrap::SetPixel error:
- invalid coordinates

CZeoFunc::CallFunction error:
- The function 'CalcArea' in the plugin 'L3DT-CORE' returned an error.

threadman_RunTiles error:
- call to inline tile function failed (non-threaded case)

threadman_RunTiles error:
- calculation aborted following errors

calc_TX_GenMapPro error
- call to calcman failed

calc_TX_GenMapPro error
- Operation failed or was aborted by user

sorry again for bad english
silent303
Member
 
Posts: 12
Joined: Sat Mar 03, 2007 7:26 pm

Postby silent303 » Sun Mar 04, 2007 10:09 pm

hi,

finally solved this by doing a mosaic map for the attribute map, this let me render the texture with 4xratio without error message.
silent303
Member
 
Posts: 12
Joined: Sat Mar 03, 2007 7:26 pm

Postby Aaron » Mon Mar 05, 2007 12:35 am

Hi Silent303,

I can't reproduce this bug. Can you please send me the debug log (to aaron@bundysoft.com). The log is located at:

C:\Documents and Settings\[your windows user name]\Application Data\Bundysoft\L3DT\[L3DT version number] \log.txt

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

Postby Aaron » Thu Mar 15, 2007 2:47 pm

Hi silent303,

Thanks for the info. I messed around a bit and found the bug, which is fixed in the upcoming release 2.5.

Best regards,
Aaron.

PS: This one was fairly subtle, so I wouldn't be too surprised if it popped up for other calculations or for particular combinations of settings.
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 8 guests

cron