View Issue Details

IDProjectCategoryView StatusLast Update
0001696FSSCPFREDpublic2008-08-07 05:14
ReporterRansom Arceihn Assigned ToWMCoolmon  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Summary0001696: SEXP camera movement always begins from 0, 0, 0
DescriptionUnless I'm missing something about the use of the set-camera-position SEXP, the camera should try to move from its last set position. Instead, whenever a movement time is set, it will invariably use 0, 0, 0 as its start position.

Using WMC's new 25/5 camera build.
TagsNo tags attached.

Activities

2008-05-26 11:27

 

cameramove.fs2 (3,820 bytes)

WMCoolmon

2008-06-29 07:36

developer   ~0009418

Fixed. The fix will be added to any future camera code enabled builds I release, as well as SVN when I commit the code.

WMCoolmon

2008-06-30 08:48

developer   ~0009426

Reopening since apparently this wasn't fixed 100%.

WMCoolmon

2008-08-05 03:01

developer   ~0009537

I think I figured out the problem. In the mission, you're moving the camera in 1 millisecond, and it's also supposed to spend 1 ms accelerating and decelerating. So it's trying to spend 2 ms accelerating/decelerating within 1 ms. That caused the camera to go at an undefined velocity, which put it at an undefined position.

The camera code should be able to handle that, and I made it smart enough to realize that it needs to move within the total time you've given it. Here's the updated build:

http://fs2source.warpcore.org/temp/wmc/cameramovefix.zip

Feel free to feed it some other screwy values to make sure I got everything.

WMCoolmon

2008-08-07 02:41

developer   ~0009541

Should be fixed in either of my latest builds.

Ransom Arceihn

2008-08-07 04:45

reporter   ~0009542

yessss

Looks like it works correctly now.

WMCoolmon

2008-08-07 05:14

developer   ~0009543

Sweet. :)

Issue History

Date Modified Username Field Change
2008-05-26 11:27 Ransom Arceihn New Issue
2008-05-26 11:27 Ransom Arceihn File Added: cameramove.fs2
2008-06-04 08:34 WMCoolmon Status new => assigned
2008-06-04 08:34 WMCoolmon Assigned To => WMCoolmon
2008-06-29 07:36 WMCoolmon Status assigned => resolved
2008-06-29 07:36 WMCoolmon Resolution open => fixed
2008-06-29 07:36 WMCoolmon Note Added: 0009418
2008-06-30 08:48 WMCoolmon Status resolved => feedback
2008-06-30 08:48 WMCoolmon Resolution fixed => reopened
2008-06-30 08:48 WMCoolmon Note Added: 0009426
2008-06-30 08:48 WMCoolmon Status feedback => assigned
2008-08-05 03:01 WMCoolmon Note Added: 0009537
2008-08-07 02:41 WMCoolmon Note Added: 0009541
2008-08-07 02:41 WMCoolmon Status assigned => feedback
2008-08-07 04:45 Ransom Arceihn Note Added: 0009542
2008-08-07 05:14 WMCoolmon Status feedback => resolved
2008-08-07 05:14 WMCoolmon Resolution reopened => fixed
2008-08-07 05:14 WMCoolmon Note Added: 0009543