Hard Light Productions Forums

Hosted Projects - FS2 Required => FreeSpace Conversion => Silent Threat: Reborn => Topic started by: Rusty_M on February 09, 2013, 02:12:40 pm

Title: Unable to run ST-R
Post by: Rusty_M on February 09, 2013, 02:12:40 pm
Sorry for my first post on this forum to be almost a moan.  I really don't want to, as this site has served me well with mods and installation instructions.

I've seen some other users have a similar problem to me.  I have FSO 3_6_16 and mediavps 3612.  I can run fsport-mediavps fine along with the standard FS2 with mediavps 3612.  I have tried str with both the 3_6_16 release build and the latest nightly build I could find (INF-20130209_r9527)

When I attempt to run the first mission in  ST-r, the first loading blob is filled, but the rest never load.  I can see from the display on my keyboard that one of my CPU cores remains at full load, whilst the others are unloaded.  I read that this could be due to the time to cache some files, but I left it for a couple of hours, and the loading screen did not progress.  I can load the mission if I toggle the mediavps off, but I'd rather not do that unless I really have to (sorry I'm a graphics whore).  I hope I've provided enough information and not breached any forum protocol here.  I'm uploading what I think is the correct log.

My system: Intel i7 950 OC'd to 4GHz, 18MB DDR3 1600MHz RAM, plenty of storage on a separate drive from the OS (Windows 7 64) Nvidia GTX 570

Any help would be greatly appreciated.

[attachment deleted by a basterd]
Title: Re: Unable to run ST-R
Post by: Jeff Vader on February 09, 2013, 02:20:26 pm
Hi! o/

It isn't unusual that a user's first post is about something not working, so no problems. There's a discussion about a similar issue in the FreeSpace Conversion board just above and apparently a fixed model file for the Typhon should do the trick. So, download  this (http://staff.hard-light.net/goober5000/temp/Typhon.zip), extract the typhon.pof from the zip and place it to \freespace2\fsport-mediavps\data\models . You can safely create the folder if it doesn't already exist.
Title: Re: Unable to run ST-R
Post by: Rusty_M on February 09, 2013, 02:40:24 pm
Thank you.  You're a scholar and a gentleman.

\o/ it works brilliantly now.  My god it's beautiful.  There's a world of difference using the MediaVP's.  It's like a different game.  I'm glad I asked for help.
Title: Re: Unable to run ST-R
Post by: gloowa on February 10, 2013, 04:05:49 pm
Hi, it seems to have encountered same issue, but placing Typhoon.pof in /fsport-mediavps/data/models/ did not fix things for me....
FSO crashes as soon as i try to load Typhoon in Tech Room.

Additional debug windows showed this:

Code: [Select]
IBX: Safety Check Failure!  The file doesn't contain enough data, deleting 'Typhon.bx'

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_16_DEBUG.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_16_DEBUG.exe! Warning + 430 bytes
fs2_open_3_6_16_DEBUG.exe! interp_configure_vertex_buffers + 962 bytes
fs2_open_3_6_16_DEBUG.exe! create_vertex_buffer + 814 bytes
fs2_open_3_6_16_DEBUG.exe! model_load + 1753 bytes
fs2_open_3_6_16_DEBUG.exe! techroom_select_new_entry + 450 bytes
fs2_open_3_6_16_DEBUG.exe! techroom_do_frame + 759 bytes
fs2_open_3_6_16_DEBUG.exe! game_do_state + 333 bytes
fs2_open_3_6_16_DEBUG.exe! gameseq_process_events + 237 bytes
fs2_open_3_6_16_DEBUG.exe! game_main + 782 bytes
fs2_open_3_6_16_DEBUG.exe! WinMain + 330 bytes
fs2_open_3_6_16_DEBUG.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_16_DEBUG.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

Any tips on overcoming the issue would be much appreciated.

[attachment deleted by a basterd]
Title: Re: Unable to run ST-R
Post by: Yarn on February 10, 2013, 04:32:36 pm
Goober probably should have included the cache file. Try this one (unzip it to your fsport-mediavps folder):
http://dl.dropbox.com/u/89353583/FreeSpace/FSPort/TyphonFix.zip (http://dl.dropbox.com/u/89353583/FreeSpace/FSPort/TyphonFix.zip)
Title: Re: Unable to run ST-R
Post by: gloowa on February 11, 2013, 09:48:15 am
Thanks, that worked.

[EDIT]
Nope. False alarm.

Code: [Select]
For ship 'GTF Ulysses', detail level
mismatch. Table has 4,
POF has 3.
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_16_DEBUG.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_16_DEBUG.exe! Warning + 430 bytes
fs2_open_3_6_16_DEBUG.exe! ship_create + 713 bytes
fs2_open_3_6_16_DEBUG.exe! parse_create_object_sub + 77 bytes
fs2_open_3_6_16_DEBUG.exe! parse_create_object + 193 bytes
fs2_open_3_6_16_DEBUG.exe! parse_wing_create_ships + 1439 bytes
fs2_open_3_6_16_DEBUG.exe! post_process_ships_wings + 506 bytes
fs2_open_3_6_16_DEBUG.exe! post_process_mission + 69 bytes
fs2_open_3_6_16_DEBUG.exe! parse_mission + 1523 bytes
fs2_open_3_6_16_DEBUG.exe! parse_main + 449 bytes
fs2_open_3_6_16_DEBUG.exe! mission_load + 215 bytes
fs2_open_3_6_16_DEBUG.exe! game_start_mission + 184 bytes
fs2_open_3_6_16_DEBUG.exe! game_enter_state + 464 bytes
fs2_open_3_6_16_DEBUG.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_16_DEBUG.exe! game_process_event + 242 bytes
fs2_open_3_6_16_DEBUG.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_16_DEBUG.exe! game_main + 782 bytes
fs2_open_3_6_16_DEBUG.exe! WinMain + 330 bytes
fs2_open_3_6_16_DEBUG.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_16_DEBUG.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

[attachment deleted by a basterd]
Title: Re: Unable to run ST-R
Post by: General Battuta on February 11, 2013, 09:54:39 am
That's an ignorable error that should only pop up on debug builds. Just play on release.
Title: Re: Unable to run ST-R
Post by: gloowa on February 11, 2013, 01:40:01 pm
OMG. How could i have missed that i'm still running debug.
<shame on me>