1.5 Content Demo1 - fxShapeReplicator lockup

#1 This is a known issue right now. It's been a bear of a problem to track down and replicate consistantly, but rest assured Matt knows about it.

#2 Thats good !! When you ll fix it we all recieve a patch or something ??
Thank you ! (I hope not via cvs I hate it)

#3 I can replicate this problem consistantly on my machine. :)

A side note: the trees change models as I get closer to them. They will look like one type of tree from far away, and as I move closer to them they switch models and become a different tree. It does this for most the trees, which is how I found this bug that locks up torque when you click on the fxShapeReplicator.


Pictures: you probably have to copy/paste the urls into your browser

http://arcadian.host.sk/tree1.JPG - further away
http://arcadian.host.sk/tree2.JPG - just a little closer


edit:

graphics card: ATI 9600
1 gig memory
2 ghz athlon

#4

Quote:
A side note: the trees change models as I get closer to them. They will look like one type of tree from far away, and as I move closer to them they switch models and become a different tree. It does this for most the trees, which is how I found this bug that locks up torque when you click on the fxShapeReplicator.

That's just the tree switching to a different LOD -- that's so it has less polygons to draw when the tree is farther away.

#5 It doesnt look right, it looks like a bug... you shouldnt notice a lod change.

#6 You can modify it with the tree source. Don't think it's provided since the trees are from a seperate product tree pack.

BTW It would probably be very helpful to Matt if you could tell him the steps you go through to consistently replicate the problem.

#7 Steps:
I load the mission up, hit F11, click the plus sign, then click on the fxShapeReplicator. Right there it locks up.

#8 Yeah, that locks up about once every 100 times I try it and never in Debug or Optimized mode.

#9 I'll have to try again, I just got a new vid card (not new, but newer than my old one) ati x800. I'll try it tonite and see if it still locks up.

#10 I don't know if this will help any but after you first put an fxShapeReplicator down you can select it and edit it fine for a little while... but drop a few more in and come back to the first one & it will lock up... also selecting one that was allready in the mission when you load it locks it up 100% of the time for me... (note this is in the forest area demo as the starter.fps doesnt have any shapereplicators that im aware of) but even adding one to starter.fps, you can work with it fine until you go select something else then come back and reselect the shape replicator... then you get a 100% lockup.... at least I do....

#11 I don't suppose it has anything to do with the leak in fxShapeReplicator::DestroyShapes? See this thread.

#12 MY findings on the issue.


Its has to do with the new SquareSize changes...i think.

#13 Huh. open CPDemo1 mission, change the terrain squareSize to 16... and try to select fxShapeReplicator - it hangs. So, it's not squareSize.

#14 Yes, but it does this on all other sizes BUT 8 (the old standard)

#15 Any news on this?

#16 Hoping for an update, as this makes me unable to use the Replicator.

#17 Working on it.

#18 Good to hear, becouse this is a large world building problem.

#19 Greetings,

Just wanted to post my observations and findings on this issue...

Oddly enough, in my case, I found that, on my XP box, replacing the pre-packaged "torqueDemo.exe" and other from-source DLL files with ones freshly-compiled on my machine made this issue disappear.

Since it is possibly relevant, I'll note that this box has a P4 3.06 CPU with Hyperthreading enabled ... and I compiled the "Torque Demo" using "Rebuild" directly after unpacking a fresh copy of the SDK, using Visual C++ Express (SP1) with PSDK R2 and default settings ... which meant that it used two compiling processes at once on my machine.

Hope this may shed some light for the Torque developers, and possibly some of the affected community members. Also, feel free to let me know if I can be of any further assistance in tracking this issue down.

Thanks kindly!
--David Quinn Ebert
--Co-Owner/CTO, Beyond-Technical Innovations

Edit:
I forgot to mention I compiled my "fresh" binaries using "Release" mode. Whoops! :-D

#20 So, I've been hacking away at this issue for a few days now, and honestly, once I compiled fresh binaries I can no longer replicate the problem. I've tried running from the compiler, clicking the binaries, debug, release, optimized....I can no longer get the app to hang no matter what I click, how I click, or what I do.

I've tried on 3 different machines, with varying specs. Not complaining, but as far as I can tell recompiling will fix your worries. If this does not work for anyone else, please post what you are doing so I can continue working on this, otherwise I'm gonna write this off my TO-FIX list.