- Status Closed
- Percent Complete
- Task Type Bug Report
- Category src
-
Assigned To
Stijn Buys - Operating System All
- Severity Medium
- Priority Very Low
- Reported Version Development
- Due in Version 0.2.0
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Project::OSiRiON
Opened by Evan Goers - 2011-02-06
Last edited by Stijn Buys - 2011-07-12
Opened by Evan Goers - 2011-02-06
Last edited by Stijn Buys - 2011-07-12
FS#7 - Rotated misc_models render in wrong positions.
A misc_model that has been rotated in certain ways does not render correctly in-game(at least when it uses a .map as the model). The expected behavior should be how it appears in Radiant.
In my testing:
A simple Z-axis rotate renders fine. Any other complex rotations, like Y-axis rotations cause it to rotate(as expected), but the origin is in the wrong place. So, theoretically, any rotation that does not move the misc_model's referenced model's origin should work fine. Any other will break.
The latest committed version of the pirate juggernaut has misc_models with this problem, so that can be used as a test case.
Closed by Stijn Buys
Tuesday, 12 July 2011, 12:06 GMT
Reason for closing: Fixed
Additional comments about closing: This issue seems compeltely resolved.
Tuesday, 12 July 2011, 12:06 GMT
Reason for closing: Fixed
Additional comments about closing: This issue seems compeltely resolved.
This bug is a bit hard to describe. Basically, rotation should be around the misc_model's referenced model's origin.
Note: a func_rotate imported from a rotated submodel will still have a wrong rotation axis.
Submodels referenced inside a submodel are still not X rotated correctly. maps/pirate/base_large was committed earlier with the bug left in as a reference. It uses maps/pirate/sections/base_large_livingspace*.map which all have submodels of their own which aren't rotating by X correctly.
My complex test cases work as expected and it is now possible to import func_rotate
from submodels. Other submodel tags, like lights flares, docks, ... should also be
imported as expected.
This issue appears to be completely fixed.