Constructor 1.5.51 player can walk through walls
by Nancy Lee · in Constructor · 10/05/2008 (2:31 am) · 4 replies
In version 1.3.0 there is collision problem. in the new version, there is still this bug. Is it because the bug is not fixed or I modeled in a wrong way??
Another Problem is that I installed version 1.3.0 then update it to v1.5.51 without registering. Now when I try to paste the Key and press the register button, it crashes. Not sure what the problem is, please advise.
Thanks for your kindly help.
Another Problem is that I installed version 1.3.0 then update it to v1.5.51 without registering. Now when I try to paste the Key and press the register button, it crashes. Not sure what the problem is, please advise.
Thanks for your kindly help.
About the author
#2
10/11/2008 (4:20 am)
Thanks a lot Travis, I changed to some simpler structure and the collision problem were gone.
#3
I originally thought it was due to alignment and export settings chopping up the geo, but I have found that every now and then it will still happen even with very simple geo.
I may have at least discovered what circumstance lead up to the issue.
It seems that once in a while after performing some operation on a piece of geo , such as CSG sub etc.. if I attempt to clone and then move or otherwise manipulate a piece of the geo it will be off the grid snap.
This has been common for me and i have previously just been adjusting the snap and correcting the alignment.
Backing up and trying the operation again always fails the same way and additionally , sometimes geo operations fail, like CSG sub or knifing etc on a particular piece but will work else where.
I found that if i either back up to a point before the error and save or if i remember to save on a regular basis and then reload at the first sign of weirdness, it solves the issue. After a fresh reload, everything again works correctly and i have never had any export issues, if the geo was sound.
It seems to be a math error that creaps in making the internal calculations no longer jive with grid position, and simply correcting the apparent mis alignment doesnt correct the error as exports can and usually will be any flavor of borked up
Moral is, if you use contructor, save often in CSX and as stated above, always save and exit , reload before exporting, just in case.
12/12/2008 (4:10 am)
I have been experiencing collision issues on export as well as other weird editing "quirks" for lack of a better description.I originally thought it was due to alignment and export settings chopping up the geo, but I have found that every now and then it will still happen even with very simple geo.
I may have at least discovered what circumstance lead up to the issue.
It seems that once in a while after performing some operation on a piece of geo , such as CSG sub etc.. if I attempt to clone and then move or otherwise manipulate a piece of the geo it will be off the grid snap.
This has been common for me and i have previously just been adjusting the snap and correcting the alignment.
Backing up and trying the operation again always fails the same way and additionally , sometimes geo operations fail, like CSG sub or knifing etc on a particular piece but will work else where.
I found that if i either back up to a point before the error and save or if i remember to save on a regular basis and then reload at the first sign of weirdness, it solves the issue. After a fresh reload, everything again works correctly and i have never had any export issues, if the geo was sound.
It seems to be a math error that creaps in making the internal calculations no longer jive with grid position, and simply correcting the apparent mis alignment doesnt correct the error as exports can and usually will be any flavor of borked up
Moral is, if you use contructor, save often in CSX and as stated above, always save and exit , reload before exporting, just in case.
Torque 3D Owner Travis Vroman
Fireslinger Studios
I'm not sure about the crashing issue, but I would say just reinstall fresh. Register 1.0.3, then upgrade.