Pro 2.5d build 20 bug: texture generation not completing
Posted: Thu Sep 11, 2008 1:43 am
Hi i think ive found a bug in Pro 2.5d build 20:
i created the following project:
http://91.135.13.31/04.proj
and generated a design map from it - didnt edit it. i then ran the generation wizard, selecting all the options. on the lightmap configuration wizard pane, i deselected cast shadows (though i dont think this has anything to do with the bug as i have experienced the same bug with this option enabled). i then let it run. i returned some time later to find the following onscreen:
i left it for a while longer hoping that maybe it would unstick itself but unfortunately it didnt and i had to cancel the render
platform configuration:
win xp (32bit) sp3
l3dt pro 2.5d build 20
core 2 quad q9550 cpu @ stock 2.83ghz (x8.5)
dfi t2r x48 lanparty mobo - fsb @ stock 333mhz
corsair dominator xms2-8500 @ 1066mhz @ 2.1v @ 5-5-5-15
ati 4870hd 512mb @ stock: core 750mhz / mem 900mhz
i doubt sound card, psu, case etc are relevant. as i mentioned i have experienced this bug before with a different project. l3dt remains responsive - it seems to me like theres some thread synchronisation issues somewhere - sorry! :s
i created the following project:
http://91.135.13.31/04.proj
and generated a design map from it - didnt edit it. i then ran the generation wizard, selecting all the options. on the lightmap configuration wizard pane, i deselected cast shadows (though i dont think this has anything to do with the bug as i have experienced the same bug with this option enabled). i then let it run. i returned some time later to find the following onscreen:
i left it for a while longer hoping that maybe it would unstick itself but unfortunately it didnt and i had to cancel the render
platform configuration:
win xp (32bit) sp3
l3dt pro 2.5d build 20
core 2 quad q9550 cpu @ stock 2.83ghz (x8.5)
dfi t2r x48 lanparty mobo - fsb @ stock 333mhz
corsair dominator xms2-8500 @ 1066mhz @ 2.1v @ 5-5-5-15
ati 4870hd 512mb @ stock: core 750mhz / mem 900mhz
i doubt sound card, psu, case etc are relevant. as i mentioned i have experienced this bug before with a different project. l3dt remains responsive - it seems to me like theres some thread synchronisation issues somewhere - sorry! :s