Author Topic: Could not load replacement texture hol_aten for ship Ramses (Read 7056 times)

Samusaaron3 · **on:** May 21, 2011, 06:31:40 pm

I recently reinstalled FreeSpace from some old discs I had, and purchased FreeSpace 2 off of Good Old Games. I installed FS2 Open with the installation tool (everything seemed to run fine).

I've been playing through the FSPort mod (and things have been going well) up until recently. For some reason I can not load the next level in the campaign (I receive the following error).

Code: [Select]

Could not load replacement texture hol_aten for ship Ramses

ntdll.dll! NtWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_12d_INF.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_12d_INF.exe! Warning + 430 bytes
fs2_open_3_6_12d_INF.exe! parse_object + 5634 bytes
fs2_open_3_6_12d_INF.exe! parse_objects + 192 bytes
fs2_open_3_6_12d_INF.exe! parse_mission + 505 bytes
fs2_open_3_6_12d_INF.exe! parse_main + 449 bytes
fs2_open_3_6_12d_INF.exe! mission_load + 215 bytes
fs2_open_3_6_12d_INF.exe! game_start_mission + 198 bytes
fs2_open_3_6_12d_INF.exe! game_enter_state + 482 bytes
fs2_open_3_6_12d_INF.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_12d_INF.exe! game_process_event + 242 bytes
fs2_open_3_6_12d_INF.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_12d_INF.exe! game_main + 782 bytes
fs2_open_3_6_12d_INF.exe! WinMain + 330 bytes
fs2_open_3_6_12d_INF.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_12d_INF.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

I have tried clearing out my FSPort files and redownloading/reinstalling, but it has not helped. I have the FSPort mod selected in the launcher, and I have "The Great War" set as my campaign in game.

I've attached my log file for reference.

Thanks!

[attachment deleted by ninja]

pecenipicek · **Reply #1 on:** May 21, 2011, 07:05:37 pm

on a hunch, (after minimal log trawl), please move the game from the "program files" path and put it to c:\games or d:\games or whatever.

Also, it appears like you have a FS1 disc in your e drive? neither for fsport nor for fs2 with mvps should you have the discs in the drive.

also, fsport doesnt need fs1 installed

Samusaaron3 · **Reply #2 on:** May 21, 2011, 08:14:53 pm

I removed my FreeSpace disk from my drive and moved my install to C:\Games, but to no avail. Same error.

I've attached my new log.

[attachment deleted by ninja]

General Battuta · **Reply #3 on:** May 21, 2011, 08:38:33 pm

Try selecting fsport_mvps instead of fsport as your mod.

mjn.mixael · **Reply #4 on:** May 21, 2011, 08:43:33 pm

Quote from: General Battuta on May 21, 2011, 08:38:33 pm

Try selecting fsport_mvps instead of fsport as your mod.

That should do it (in theory) because the maps are not in FSPort, they are in the FSPort-Mvps... which leaves me with the question of why the game was even searching for them if he was only running FSPort... I can't recall exactly how they are set up, but I was pretty sure it was in such a way that it wouldn't search for them if only FSPort was selected.

Samusaaron3 · **Reply #5 on:** May 21, 2011, 09:14:10 pm

I'm getting a different error now, though the game seems to run fine once I dismiss it (and everything is prettier!)

Code: [Select]

Subsystem "communications" in model "fighter02.pof" is represented as "communication" in ships.tbl.  Although FS2_OPEN 3.6 and later will catch and correct this error, earlier versions (as well as retail FS2) will not.  You are advised to fix this if you plan to support earlier versions of FreeSpace.

ntdll.dll! NtWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_12d_INF.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_12d_INF.exe! Warning + 430 bytes
fs2_open_3_6_12d_INF.exe! do_new_subsystem + 241 bytes
fs2_open_3_6_12d_INF.exe! read_model_file + 16204 bytes
fs2_open_3_6_12d_INF.exe! model_load + 754 bytes
fs2_open_3_6_12d_INF.exe! mission_parse_handle_late_arrivals + 185 bytes
fs2_open_3_6_12d_INF.exe! mission_parse_maybe_create_parse_object + 340 bytes
fs2_open_3_6_12d_INF.exe! post_process_ships_wings + 93 bytes
fs2_open_3_6_12d_INF.exe! post_process_mission + 49 bytes
fs2_open_3_6_12d_INF.exe! parse_mission + 1531 bytes
fs2_open_3_6_12d_INF.exe! parse_main + 449 bytes
fs2_open_3_6_12d_INF.exe! mission_load + 215 bytes
fs2_open_3_6_12d_INF.exe! game_start_mission + 198 bytes
fs2_open_3_6_12d_INF.exe! game_enter_state + 482 bytes
fs2_open_3_6_12d_INF.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_12d_INF.exe! game_process_event + 242 bytes
fs2_open_3_6_12d_INF.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_12d_INF.exe! game_main + 782 bytes
fs2_open_3_6_12d_INF.exe! WinMain + 330 bytes
fs2_open_3_6_12d_INF.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_12d_INF.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

Edit: Now the next level won't load...

Code: [Select]

Couldn't open texture 'shieldhit01a'
referenced by model 'bomber01.pof'

ntdll.dll! NtWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_12d_INF.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_12d_INF.exe! Warning + 430 bytes
fs2_open_3_6_12d_INF.exe! model_load_texture + 361 bytes
fs2_open_3_6_12d_INF.exe! read_model_file + 16508 bytes
fs2_open_3_6_12d_INF.exe! model_load + 754 bytes
fs2_open_3_6_12d_INF.exe! mission_parse_handle_late_arrivals + 185 bytes
fs2_open_3_6_12d_INF.exe! mission_parse_maybe_create_parse_object + 340 bytes
fs2_open_3_6_12d_INF.exe! post_process_ships_wings + 93 bytes
fs2_open_3_6_12d_INF.exe! post_process_mission + 49 bytes
fs2_open_3_6_12d_INF.exe! parse_mission + 1531 bytes
fs2_open_3_6_12d_INF.exe! parse_main + 449 bytes
fs2_open_3_6_12d_INF.exe! mission_load + 215 bytes
fs2_open_3_6_12d_INF.exe! game_start_mission + 198 bytes
fs2_open_3_6_12d_INF.exe! game_enter_state + 482 bytes
fs2_open_3_6_12d_INF.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_12d_INF.exe! game_process_event + 242 bytes
fs2_open_3_6_12d_INF.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_12d_INF.exe! game_main + 782 bytes
fs2_open_3_6_12d_INF.exe! WinMain + 330 bytes
fs2_open_3_6_12d_INF.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_12d_INF.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

[attachment deleted by ninja]

mjn.mixael · **Reply #6 on:** May 21, 2011, 09:35:54 pm

The checksum for FSPort-Missions.vp is off, also I'm not sure what FSPort3_2-fix.vp is. I would recommend downloading FSport from here.

However, someone more versed in these logs might see something I didn't.

General Battuta · **Reply #7 on:** May 21, 2011, 09:47:13 pm

If you play with a release (r) build instead of a debug (d) build do those errors still pop up?

Samusaaron3 · **Reply #8 on:** May 21, 2011, 09:54:20 pm

Quote from: General Battuta on May 21, 2011, 09:47:13 pm

If you play with a release (r) build instead of a debug (d) build do those errors still pop up?

That seems to have fixed it (for now at least)

Thanks!

General Battuta · **Reply #9 on:** May 21, 2011, 09:59:39 pm

As a last check, is your MediaVPs folder called mediavps or mediavps_3612?

If the latter (it should be), find the mod.ini file in fsport_mvps and change any reference to 'mediavps' to 'mediavps_3612'.

Dragon · **Reply #10 on:** May 22, 2011, 02:59:33 am

These errors are not important, the first one is caused by careless subsystem naming on a HTL ship model, while the second one is due to shield mesh somehow ending up with a texture assigned (a modeller's mistake, easy to fix).

Galemp · **Reply #11 on:** May 22, 2011, 03:23:37 am

Yes, I suppose with a certain combination of factors you would get debug errors. Play using a Release build unless you're a developer, or you are getting errors, crashes and warnings with a Release build.

Zacam · **Reply #12 on:** May 22, 2011, 11:26:11 pm

The hol_aten issue comes from the ;;FSO flag in the "Retail" FSPort missions being present, regardless of the graphics being present in the FSPort_MediaVPs.

Either the graphic needs to also be in the FSPort package or needs to not be present in-mission. As the other solution of copying the mission into FSPort-MediaVP's to include the ;;FSO -only- changes probably is not all that viable. At the moment.

Galemp · **Reply #13 on:** June 01, 2011, 12:13:45 am

This only pops up if you're using FSO, on a debug build, without the MediaVPs enabled, which is highly irregular.

Zacam · **Reply #14 on:** June 01, 2011, 08:33:34 pm

If Port is going to be one thing, and the Port-MediaVPs are an OPTIONAL compliment to that, then why have features in that require Port to have the Port-MediaVPs be present in order to work?

Hiding it behind an ;;FSO tag just means that Retail FS2 exe can't see it. But even a Release build has it's limits on not liking finding stuff it's told it's supposed to have.

Here, hold on to this bucket, would you?

Goober5000 · **Reply #15 on:** June 02, 2011, 12:30:36 pm

They are optional. If the texture isn't found, it isn't replaced. Pretty straightforward. Especially since this particular texture replacement is only applicable on an MVP model.

However, the error message definitely needs to be commensurate with the issue. It's meant to be a notification to modders, saying, "By the way, the texture you're assuming is there really isn't, so I'm not going to use it. Just FYI in case you misspelled something." So it should be a line in the debug log rather than an in-your-face warning.

And what does a bucket have to do with anything?

Zacam · **Reply #16 on:** June 03, 2011, 07:38:58 pm

Maybe the Texture Replacement has a bug in it then.
If "+old:" can't be found, it will continue on it's merry way so long as it can find "+new:".
If it can't find "+new:" (regardless of whether or not "+old:" exists or can be found), it throws an absolute wobbler.

Try it yourself and note that it will never complain about not finding "+old:".
And that's what the bucket has to do with this, there wasn't one, so there was nothing to hold on to.
(the buckets name is "+new:" btw)

Goober5000 · **Reply #17 on:** June 03, 2011, 08:30:57 pm

Aha. Yes, that would be a usability bug.

News:

Author Topic: Could not load replacement texture hol_aten for ship Ramses (Read 7056 times)

Samusaaron3

Could not load replacement texture hol_aten for ship Ramses

pecenipicek

Re: Could not load replacement texture hol_aten for ship Ramses

Samusaaron3

Re: Could not load replacement texture hol_aten for ship Ramses

General Battuta

Re: Could not load replacement texture hol_aten for ship Ramses

mjn.mixael

Re: Could not load replacement texture hol_aten for ship Ramses

Samusaaron3

Re: Could not load replacement texture hol_aten for ship Ramses

mjn.mixael

Re: Could not load replacement texture hol_aten for ship Ramses

General Battuta

Re: Could not load replacement texture hol_aten for ship Ramses

Samusaaron3

Re: Could not load replacement texture hol_aten for ship Ramses

General Battuta

Re: Could not load replacement texture hol_aten for ship Ramses

Dragon

Re: Could not load replacement texture hol_aten for ship Ramses

Galemp

Re: Could not load replacement texture hol_aten for ship Ramses

Zacam

Re: Could not load replacement texture hol_aten for ship Ramses

Galemp

Re: Could not load replacement texture hol_aten for ship Ramses

Zacam

Re: Could not load replacement texture hol_aten for ship Ramses

Goober5000

Re: Could not load replacement texture hol_aten for ship Ramses

Zacam

Re: Could not load replacement texture hol_aten for ship Ramses

Goober5000

Re: Could not load replacement texture hol_aten for ship Ramses