[v2.8 build 16] Incorrect Attribute Map Progress
Posted: Fri Mar 19, 2010 11:38 pm
Hi Aaron, I'm currently building the attribute map at 4x quality for a large terrain of size 3712 × 7680.
It's currently at the stage of 'calculating land types' and it seems that both the time estimate and percentage progress shown in the main window are using what appears to be more like the width of the terrain squared instead of width * length. This was apparent when, as it has just got past what looks like 1/3 of the length of the map the progress went from 98, 99%, etc. to blank and the time is now showing 'Indeterminate'. Looks like I've got a bit longer to wait
It's not a big problem, but hopefully it's also pretty easy to fix. I should point out I haven't tried other maps with other ratios so I hope this isn't just a random occurrence!
One thing I'd also like to mention is that support for multiprocessing is really needed for this stage. You probably already know (I think it's on your todo list even) so I don't want to grumble too strongly. However it is by far the slowest part of any map creation for me, and I guess I've been spoiled by the speed of the other stages on my Q6600, but it'd be great if this was tackled soon.
It's currently at the stage of 'calculating land types' and it seems that both the time estimate and percentage progress shown in the main window are using what appears to be more like the width of the terrain squared instead of width * length. This was apparent when, as it has just got past what looks like 1/3 of the length of the map the progress went from 98, 99%, etc. to blank and the time is now showing 'Indeterminate'. Looks like I've got a bit longer to wait
It's not a big problem, but hopefully it's also pretty easy to fix. I should point out I haven't tried other maps with other ratios so I hope this isn't just a random occurrence!
One thing I'd also like to mention is that support for multiprocessing is really needed for this stage. You probably already know (I think it's on your todo list even) so I don't want to grumble too strongly. However it is by far the slowest part of any map creation for me, and I guess I've been spoiled by the speed of the other stages on my Q6600, but it'd be great if this was tackled soon.