View Issue Details

IDProjectCategoryView StatusLast Update
0001144FSSCPgameplaypublic2006-12-20 10:43
ReporterARSPR Assigned Totaylor  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionwon't fix 
PlatformP4 2.8 HT - 1.5GB - 7800GSOSWindows XPOS VersionSP2
Product Version3.6.9 
Summary0001144: GTD Orion colisision with something invisible
DescriptionIn the mission "Nowhere Safe to Hide" from "Into The Hall Of Valhalla" campaign, GTD Bangladesh, (an Orion class one), colides with something invisible just after starting its turn from waypoint2 to waypoint3 (about 4:15 min left in its mission timer, about 7:50 in mission time). Then it stops so it can't finish its fly path.

At this possition, the Orion is near a Ganimede Ring but it is not touching it or any other ship.

When GTD Bangladesh has been stopped it's hull strength blinks as it were been hit or colliding with something.

It happens with Mediavps 3.6.8. zeta HTL Orion. Retail Orion works fine.
Steps To ReproduceI attach the conflictive mission. It works fine with retail or mediavps tables so you don't need to install campaign vps (although ship and weapon settings can be different, but we aren't testing campaign gameplay, are we?).
Additional InformationI don't know if it is some kind of AI bug or some model problem. I've set this bug severity to major as it can be a huge problem in other missions.

As I've said in Description, if you extract capital01.pof from retail FS2 and you copy it to mediavps\data\models to override the HTL one, there is no colision.
TagsNo tags attached.

Activities

2006-11-12 10:10

 

thesource2

2006-11-12 11:10

reporter   ~0007104

Looks like data error rather than code one. Perhaps category should be changed to MediaVP

ARSPR

2006-12-05 19:54

reporter   ~0007238

* bump *

Has any SCP master been able to take a look at this?

(If it is some kind of bug inside the HTL Orion, it would be nice to solve it before the next media vps release).

taylor

2006-12-05 20:15

administrator   ~0007239

I'll try and take a look at it tonight.

taylor

2006-12-08 07:30

administrator   ~0007282

It's hitting the Ganymede. The HTL Orion has a slightly larger bounding box (by only a couple of %), partciularly in the height. The Ganymede has a bounding box larger than it really needs to be in height. So, depeding on the orientation of the Ganymede, it's possible to catch the bottom corner of the orion bounding box and trigger a collision.

This isn't a code issue, and isn't likely to be fixed with data (unless the Orion gets redone again anytime soon). The best fix is just to move the Orion's waypoint in that mission either up or to the left by 15-20 meters. Even with the retail Orion model it just barely squeezes past the Ganymede, so the placement is problematic in either case, it just happens to be slightly worse with the HTL version.

taylor

2006-12-20 10:43

administrator   ~0007311

I guess that you could technically call this a bug caused by the HTL Orion, but I think it's pretty safe to say that it's going to officially be considered a mission bug. The positioning is so close that it's simply amazing that it doesn't hit with retail data. There isn't anything we can do about this in the code, and I don't think that the Orion model is going to get remade to make up for the <15m difference in size on a particular side just to address this problem.

Marking as a "won't fix" for the MediaVP aspect of it, but this should really be considered something for the mission maker to fix.

Issue History

Date Modified Username Field Change
2006-11-12 10:10 ARSPR New Issue
2006-11-12 10:10 ARSPR File Added: 1-07NowhereSafeToHide.fs2
2006-11-12 11:10 thesource2 Note Added: 0007104
2006-12-05 19:54 ARSPR Note Added: 0007238
2006-12-05 20:15 taylor Note Added: 0007239
2006-12-08 07:30 taylor Note Added: 0007282
2006-12-20 10:43 taylor Status new => resolved
2006-12-20 10:43 taylor Resolution open => won't fix
2006-12-20 10:43 taylor Assigned To => taylor
2006-12-20 10:43 taylor Note Added: 0007311