Hard Light Productions Forums
Hosted Projects - FS2 Required => Blue Planet => Topic started by: LordPomposity on January 07, 2013, 06:39:33 am
-
Guess who gets to be the first person who (probably) can't follow simple instructions. :p
Me!
(http://img204.imageshack.us/img204/2357/screen0216.jpg)
log attached (exceeded character limit as part of post). Thanks for the update, and I'd appreciate any help.
Icarus was amazing.
EDIT: this is from a clean install of blueplanet and blueplanet2. I deleted the original folders before installing the new ones.
[attachment deleted by a basterd]
-
Hmmm.....
TBM => Starting parse of 'mv_core-hdg.tbm' ...
TBM => Starting parse of 'mv_root-hdg.tbm' ...
That's the problem. Not your fault (probably mine), will post fix soon.
EDIT: Please download this: http://blueplanet.fsmods.net/mv_core-hdg.tbm and place it in blueplanet2\data\tables
-
Thank you.
-
Sorry to have to toss my own slightly moth-eaten hat into the ring, but I've encountered the same error, while the solution provided above failed to fix it. Here's the pastebin of my own fs2_open, if it should assist any, and it might help to mention that the latest install was performed over a prior install of WiH - that hasn't seen the updated HUD/Karuna et al.
http://pastebin.com/bqmqHY5Q
-
Did you delete everything in blueplanet2\data\, except for the file linked here?
-
Did you delete everything in blueplanet2\data\, except for the file linked here?
If you mean that the /data folder is empty aside from the /tables folder, which only contains 'mv_core-hdg.tbm', no change has been visible from such.
http://pastebin.com/YuwjmpQP <- Latest pastebin, of course.
-
Also still encountering the issue, even after another complete re-install (after which I created /data/tables and pasted in the provided patch). Log attached below.
When I'm loading Dreamscape in debug, I get two errors that don't seem relevant to the problem (and were also present before adding the tbm file), but I'll post them here anyways.
Not all subsystems in model "capital03.pof" have a record in ships.tbl.
This can cause game to crash.
List of subsystems not found from table is in log file.
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! Warning + 495 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! do_new_subsystem + 482 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! read_model_file + 5679 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! model_load + 754 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! mission_parse_handle_late_arrivals + 186 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! mission_parse_maybe_create_parse_object + 369 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! post_process_ships_wings + 93 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! post_process_mission + 69 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! parse_mission + 1595 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! parse_main + 449 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! mission_load + 215 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_start_mission + 184 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_enter_state + 559 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_process_event + 242 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_main + 782 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! WinMain + 328 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! __tmainCRTStartup + 283 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! WinMainCRTStartup + 13 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
Couldn't open texture 'purple_glow'
referenced by model 'capital03.pof'
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! Warning + 495 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! read_model_file + 14643 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! model_load + 754 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! mission_parse_handle_late_arrivals + 186 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! mission_parse_maybe_create_parse_object + 369 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! post_process_ships_wings + 93 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! post_process_mission + 69 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! parse_mission + 1595 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! parse_main + 449 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! mission_load + 215 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_start_mission + 184 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_enter_state + 559 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_process_event + 242 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! game_main + 782 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! WinMain + 328 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! __tmainCRTStartup + 283 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! WinMainCRTStartup + 13 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
EDIT: Took a few stabs in the dark by myself. Reinstalling mediavps did not solve the problem. Next thing I'll try is a fresh install of FS2 and FS2 open.
[attachment deleted by a basterd]
-
I'll leave the troubleshooting to The_E but
PLR => Verifying 'Space Hitler.plr' with version 0...
PLR => Parsing: Flags...
PLR => Verifying complete!
PLR => Verifying 'Space Tojo.plr' with version 0...
PLR => Parsing: Flags...
PLR => Verifying complete!
explain yourself pilot :colbert:
-
Space Hitler was created to play Silent Threat Reborn, on the basis of the fan theory that the player in Silent Threat is Bosch.
His spiritual successor, Space Tojo, was created to play Wings of Dawn.
That last sentence probably does not help my case.
Anyways, a completely fresh FS2 install does not solve the problem. :/
-
I assume that includes cleaning out all /data/ folders?
What happens if you crank the resolution to 1680x1050?
-
What happens if you crank the resolution to 1680x1050?
That does it.
The aspect ratio of everything is now slightly off, but I'd been playing like this for a long time before I switched to 1400x1050, so I think I'll live.
Thank you!
-
Thank you for spotting that we might need to do some work on our hud gauges table :o
-
I assume that includes cleaning out all /data/ folders?
What happens if you crank the resolution to 1680x1050?
Setting to a 16:10 ratio managed to fix it up here too, thank you very much!
And here I thought my 1280x1024 resolution was being sensible...
-
I had double hud, chaning the resolution solved it.
-
No solution so far? Changing resolution helps, but the picture looks poor in any resolution but native (1280x1024).
-
You could try running in a window (in the launcher under advanced settings: Dev Tool -> Run in Window). That way you'll have the correct resolution to avoid the double HUD, and it won't be rendered in a non-native resolution (which as you point out looks terrible on LCD monitors).
-
You could try running in a window (in the launcher under advanced settings: Dev Tool -> Run in Window). That way you'll have the correct resolution to avoid the double HUD, and it won't be rendered in a non-native resolution (which as you point out looks terrible on LCD monitors).
Tried this, and it worked. Not ideal, but it makes the game playable again, which is definitely enough.
-
What is the issue with adding $Required Aspect: Wide Screen
to the first hdg entry?