View Issue Details

IDProjectCategoryView StatusLast Update
0000939The Babylon ProjectAsset - Modelpublic2013-02-23 07:29
ReporterVidmasterAssigned ToFUBAR-BDHR 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionnot fixable 
Product VersionZathras 2.7 
Target VersionFixed in Version 
Summary0000939: Crazy subsystem rotation bug
DescriptionI have noticed a funny bug, I am not sure if this is our fault or a bug in the RC1: With my build, when you increase time compression, one of the EA Explorer vessel starts rotating as if it were a part of the other.
Steps To Reproduce- use recent Zathras, modeltest mod and current RC1 SSE build
- load the model test mission
- look towards the EA Explorers
- increase time compression
Additional InformationMy money is on a code bug. If yes, please create a mantis entry there.
TagsNo tags attached.

Activities

Vidmaster

2013-01-27 20:28

manager  

screenshots.zip (884,553 bytes)

FUBAR-BDHR

2013-01-27 22:57

manager   ~0001106

I don't think this is actually a bug. If you look at the ships at mission start they do the same thing but then stop. What is happening here is the 2 ships are colliding. Cap ships check spheres not actual contact and since the ships are so long they have a big sphere radius. So the engine sees it as a collision and since it hit a rotating object it moves in that direction. You can verify this by targeting a ship and see that the hull value is blinking as if it is being hit.

Now why it happens more often when time compression is enabled I have no idea. That part may be a bug.

FUBAR-BDHR

2013-02-23 07:29

manager   ~0001126

Definitely a collision code issue. Like many others not fixable without a complete rewrite of the collision code which isn't going to happen anytime soon.

Issue History

Date Modified Username Field Change
2013-01-27 20:28 Vidmaster New Issue
2013-01-27 20:28 Vidmaster Status new => assigned
2013-01-27 20:28 Vidmaster Assigned To => FUBAR-BDHR
2013-01-27 20:28 Vidmaster File Added: screenshots.zip
2013-01-27 22:57 FUBAR-BDHR Note Added: 0001106
2013-02-23 07:29 FUBAR-BDHR Note Added: 0001126
2013-02-23 07:29 FUBAR-BDHR Status assigned => closed
2013-02-23 07:29 FUBAR-BDHR Resolution open => not fixable