View Issue Details

IDProjectCategoryView StatusLast Update
0001869FSSCPFREDpublic2010-05-19 05:20
ReporterFUBAR-BDHR Assigned Tokarajorma  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version3.6.9 
Summary0001869: Fix warp doesn't work on on player ships in Inferno builds
DescriptionThat pretty much sums it up. A player ship with warp disabled by break warp does not warp out when fix warp is enabled. The alt-j works and the AI ships in Alpha/Beta warp out but not the player. Works fine in regular builds.
Additional Information3.6.10 Inferno build from the r5032 SVN. Also tested with Kara's Inferno build from 12/29. Noticed playing Raider Wars mission 1 in TBP. Only modification from the stock mission is I made Alpha 1 invincible so I could take some screenshots on insane without dying.
TagsNo tags attached.

Activities

2009-01-12 20:07

 

rw01 - motfl.fs2 (56,144 bytes)

Goober5000

2009-01-20 00:46

administrator   ~0010546

I've looked at the code and I don't see any way that the behavior would differ between Inferno and non-Inferno builds.

Have you guys cleaned out all the debug errors in TBP? I would download it to test, but I don't want to click through a zillion debug warnings.

FUBAR-BDHR

2009-01-20 01:37

developer   ~0010551

There are still tons of MOI warnings and the over 130 ship warnings. I couldn't see why one would work and not the other either. Doesn't seem to be anything Inferno specific in there but the code is way beyond me.

Strange thing is all the AI ships jump you just don't. So it's activating the alt-j sequence but you don't get the subspace drive message or leave.

Goober5000

2009-01-20 02:16

administrator   ~0010556

Last edited: 2009-01-20 02:16

Well, maybe the Inferno build you're using was built with undated code.

I'm sorry to say this, but unless you can get TBP to clean up all their debug warnings, or you can reproduce this error with an unmodded mission, I'll have to close this issue as won't-fix.

karajorma

2009-01-23 22:17

administrator   ~0010595

I'll give it a try in FS2 first.

2009-02-01 05:11

 

1869.fs2 (4,811 bytes)

FUBAR-BDHR

2009-02-01 05:12

developer   ~0010630

Attached FS2 mission. Just hit alt-j when you get the message.

karajorma

2009-02-01 14:35

administrator   ~0010632

I tried it. Worked perfectly for me. Before 10 seconds I couldn't warp out, after 10 I could. I'll upload my builds in a little bit.

FUBAR-BDHR

2009-02-07 00:55

developer   ~0010654

Just a reminder to post that build.

karajorma

2009-02-07 08:19

administrator   ~0010655

http://www.freespacefaq.com/Misc-Downloads/Builds/Inferno_Builds_29thJan2009.7z

I'd uploaded them a while back but just forgot to link them here.

FUBAR-BDHR

2009-02-07 18:26

developer   ~0010656

Well that inferno build works. Strange that your 12/29 build didn't and my 2 didn't. I'll try building a new one later today and see if that one works as well.

FUBAR-BDHR

2009-02-09 00:29

developer   ~0010661

Last edited: 2009-02-09 04:03

Just built a debug Inferno r5063 and it doesn't work. It's even weirder than before the break warp doesn't work either. I don't get either the can't warp message or the subspace drive engaged message. Very strange. I did a clean build using VS2008 express.

Update: I just did a regular debug build and it works. Even used the same project file as before just remove the INF_BUILD. It's getting stranger and stranger.

Update 2: Rebuilt the inferno build again. Still doesn't work. Could it be something with VS2008 express?

karajorma

2009-03-12 20:52

administrator   ~0010734

Did you try that multiplayer Inferno build I posted?

FUBAR-BDHR

2009-03-13 00:07

developer   ~0010736

Just tried it and it does work.

karajorma

2009-03-28 20:27

administrator   ~0010780

If this is working with 3.6.10 RCs I think we might as well close this as a Mantis report and try to figure it out on the forum instead.

FUBAR-BDHR

2009-03-29 01:18

developer   ~0010781

Did some more experimenting. The more I tried to compile it the more went wrong. First time the same jump problem second it wouldn't even rebuild. Then I could build part of it but not another. Finally I did a new checkout on my C: drive instead of a network drive. Worked the first time. I'm guessing that MS 2008 Express isn't liking my Novell Netware server drives. Looks like it's not releasing the lock on files at times then trying to open the locked file causing strange things to happen.

So it looks more like a compatibility issue on my end. Don't suppose there is anyone else running an old Netware 6 server so this can probably be closed.

Issue History

Date Modified Username Field Change
2009-01-12 20:06 FUBAR-BDHR New Issue
2009-01-12 20:07 FUBAR-BDHR File Added: rw01 - motfl.fs2
2009-01-15 14:13 karajorma Status new => assigned
2009-01-15 14:13 karajorma Assigned To => karajorma
2009-01-20 00:46 Goober5000 Note Added: 0010546
2009-01-20 01:37 FUBAR-BDHR Note Added: 0010551
2009-01-20 02:16 Goober5000 Note Added: 0010556
2009-01-20 02:16 Goober5000 Note Edited: 0010556
2009-01-23 22:17 karajorma Note Added: 0010595
2009-02-01 05:11 FUBAR-BDHR File Added: 1869.fs2
2009-02-01 05:12 FUBAR-BDHR Note Added: 0010630
2009-02-01 14:35 karajorma Note Added: 0010632
2009-02-07 00:55 FUBAR-BDHR Note Added: 0010654
2009-02-07 08:19 karajorma Note Added: 0010655
2009-02-07 18:26 FUBAR-BDHR Note Added: 0010656
2009-02-09 00:29 FUBAR-BDHR Note Added: 0010661
2009-02-09 03:05 FUBAR-BDHR Note Edited: 0010661
2009-02-09 04:03 FUBAR-BDHR Note Edited: 0010661
2009-03-12 20:52 karajorma Note Added: 0010734
2009-03-13 00:07 FUBAR-BDHR Note Added: 0010736
2009-03-28 20:27 karajorma Note Added: 0010780
2009-03-29 01:18 FUBAR-BDHR Note Added: 0010781
2009-03-29 07:50 karajorma Status assigned => resolved
2009-03-29 07:50 karajorma Resolution open => no change required
2010-05-19 05:20 Goober5000 Status resolved => closed