View Issue Details

IDProjectCategoryView StatusLast Update
0001722FSSCPgameplaypublic2008-12-05 23:50
ReporterBlackWolf Assigned ToGoober5000  
PriorityurgentSeveritymajorReproducibilitysometimes
Status resolvedResolutionfixed 
Product Version3.6.9 
Summary0001722: Spinning Cargo
DescriptionCargo placed as one container, but then changed to another will spin in place on its axis. Seems to affect some computers but not all. Makes docking impossible, and the only way I found to rectify it was to delete the cargo entirely and replace.
TagsNo tags attached.

Activities

ARSPR

2008-07-09 13:00

reporter   ~0009437

IIRC it's a problem with POFs with no inertia.

Run a debug build and check if you get a warning about the conflictive model. In this situation, it's a model error rather than a bug. (Media vps 3.6.10 beta have several models with no inertia).

BlackWolf

2008-07-10 14:25

reporter   ~0009440

It's not MOI. The cargo isn't interacting with anything, and I git it for the first time with the TAC-1 - still a retail model with [V]s original MOI data.

Goober5000

2008-08-12 05:06

administrator   ~0009558

This is a pretty severe bug that needs to be fixed ASAP... for top secret reasons. As such, I'm assigning it to karajorma, who's been a pretty reliable bug fixer lately. :)

I have a hunch that this MAY be related to Backslash's physics changes. This is only a hunch though, and could be completely wrong.

Goober5000

2008-08-26 01:29

administrator   ~0009611

As I posted in the STOP SPINNING thread, I think I might have fixed this. Please download the build I linked there and test it out.

chief1983

2008-10-08 22:27

administrator   ~0009839

Should probably close this if it's been fixed.

phreak

2008-11-18 15:32

developer   ~0010217

Has this issue been resolved then?

chief1983

2008-11-18 15:51

administrator   ~0010223

CP5670 reported it was still happening to him in the forum thread.

chief1983

2008-11-18 22:04

administrator   ~0010226

I was unable to reproduce this, it may only affect old missions and not be a problem in current builds, and there may be no easy way to prevent it happening. It may come down to requiring patches for old missions but I'm not sure that'll have to happen.

chief1983

2008-12-02 21:13

administrator   ~0010321

As soon as I mark this resolved someone is going to say they can reproduce it with a new mission...

Shade

2008-12-05 22:09

developer   ~0010354

Can't seem to replicate this either.

chief1983

2008-12-05 23:50

administrator   ~0010360

Ok. If it's only PI having a problem there's just going to have to be a patch to fix it.

Issue History

Date Modified Username Field Change
2008-07-08 14:33 BlackWolf New Issue
2008-07-09 13:00 ARSPR Note Added: 0009437
2008-07-10 14:25 BlackWolf Note Added: 0009440
2008-08-12 05:04 Goober5000 Status new => assigned
2008-08-12 05:04 Goober5000 Assigned To => Goober5000
2008-08-12 05:04 Goober5000 Assigned To Goober5000 => karajorma
2008-08-12 05:06 Goober5000 Note Added: 0009558
2008-08-12 05:06 Goober5000 Priority normal => urgent
2008-08-12 05:06 Goober5000 Severity minor => major
2008-08-12 05:06 Goober5000 Status assigned => confirmed
2008-08-26 01:29 Goober5000 Note Added: 0009611
2008-08-26 01:29 Goober5000 Status confirmed => assigned
2008-08-26 01:29 Goober5000 Assigned To karajorma => Goober5000
2008-10-08 22:27 chief1983 Note Added: 0009839
2008-10-08 22:27 chief1983 Status assigned => feedback
2008-11-18 15:32 phreak Note Added: 0010217
2008-11-18 15:51 chief1983 Note Added: 0010223
2008-11-18 22:04 chief1983 Note Added: 0010226
2008-12-02 21:13 chief1983 Note Added: 0010321
2008-12-05 22:09 Shade Note Added: 0010354
2008-12-05 23:50 chief1983 Note Added: 0010360
2008-12-05 23:50 chief1983 Status feedback => resolved
2008-12-05 23:50 chief1983 Resolution open => fixed