Game Development Community

Atlas Bugs

by Vincent BILLET · in Torque Game Engine Advanced · 09/16/2005 (1:01 pm) · 6 replies

I've noticed two bugs in Atlas
1) GenerateCHU freeze when height amplitutide is too important.
2) Atlas object crashes regulary with heightmaps >8192x8192. (Access violations 0xC0000005, read of adress 0x000000000)

Another bug :
Terrain loading is very very long for terrains of 8192x8192 and more. (>2 minutes)

When are coming back to Atlas Ben?
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine Advanced


Torque Owner Valador, Inc.
Valador Inc
#1
09/16/2005 (2:28 pm)
I noticed a major speed gain by changing the parameters by changing these parameters in atlasGen.h/cpp

void update(F32 baseMaxError, Point2I a, Point2I r, Point2I l);
void update(F32 baseMaxError, const Point2I& a, const Point2I& r, const Point2I& l);

The copying and ctor of Point2I was showing up on my profilier.

Torque Owner Vincent BILLET
Default Studio Name
#2
09/16/2005 (3:01 pm)
Thank you for your reply Kevin, but
Before : My terrain crashes TSE.
After : It crashes my computer (direct reboot) :(

Associate Kyle Carter
#3
09/17/2005 (8:24 pm)
I will get back to Atlas once TDN is launched for SDK owners. I'll be doing a revamp of the content creation tools to be significantly more powerful and intuitive.

@Kevin: Thanks for the fix, does that also give a speedup in release mode?

Torque Owner Vincent BILLET
Default Studio Name
#4
09/18/2005 (2:25 am)
Quote:I'll be doing a revamp of the content creation tools to be significantly more powerful and intuitive
Can we have further explanations about this revamp, or will it keep secret until MS3 release?
For the momment, I have many files (RAW and CHU) which crash Atlas. If you want to have a look to these files, I'll send you them.

Edit : I've also noticed some collision bugs. In some cases, Player will fall trough the terrain :)... It's funny but very surprising. (I can reproduce this bug)

Torque Owner Valador, Inc.
Valador Inc
#5
09/19/2005 (6:49 am)
Ben,

I'm not sure about a release speed-up. I was using AMD's profiler which won't let me profile in debug. Maybe I can find some time to profile on V-Tune after I talk our guys into buying it for me.

It was being called a lot so, at the very least, it doesn't hurt.

I found my biggest problem with the speed was more of an issue of not understanding the parameters well and setting something that caused huge processing times.

Associate Kyle Carter
#6
09/21/2005 (5:07 am)
Well, I'm talking about a many minutes to few seconds speedup. So you wouldn't need a tool to spot it. :)