[Lowcorn]

Hi Folks!

So i'm getting this error-

mv_assets-wep.tbm(line 111):
Error: Required token = [#End] or [$Name:], found [$Model File:      S_Rockeye.pof].

ntdll.dll! ZwWaitForSingleObject + 12 bytes
KERNELBASE.dll! WaitForSingleObject + 18 bytes
fred2_open_3_7_2_SSE.exe! <no symbol>
fred2_open_3_7_2_SSE.exe! <no symbol>
fred2_open_3_7_2_SSE.exe! <no symbol>

now what i cant figure out is that mv_Assets-wep.tbm isn't anything i have inside the mod folder i'm using. At first i thought it might be from the settings in my mod.ini but changing the primary and secondary lists to different other options doesn't change the effect. And leaving them 100% blank does nothing ether.

Anyone have thoughts?

Thanksss!


side note,
I seem to have hit the cap for how many ships i can have >.>

[General Battuta]

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

mv_assets-wp.tbm is a file from the MediaVPs.

[AdmiralRalwood]

now what i cant figure out is that mv_Assets-wep.tbm isn't anything i have inside the mod folder i'm using. At first i thought it might be from the settings in my mod.ini but changing the primary and secondary lists to different other options doesn't change the effect. And leaving them 100% blank does nothing ether.

mv_assets-wep.tbm is in the MediaVPs' "MV_Assets.vp" file. Changing your mod.ini won't do anything until you change mods in the launcher, because it won't re-parse the mod.ini until you re-select the mod. That being said, the error makes no sense. Judging by the line number, it's the 3.6.12 MediaVPs, but just as in the 2014 MediaVPs, that line is immediately preceded by a "$Name:" line, so for FSO to be looking for a "$Name:" line again should require it to have failed to find any valid entries, but "$Model file:" is a field dating back to retail. On the other hand, the 3.6.12 MediaVPs are quite outdated at this point, and new mods should really be using the 2014 MediaVPs instead. Still, if you want to help us figure out this bizarre error, please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

fred2_open_3_7_2_SSE.exe

In addition to the 3.6.12 MediaVPs being out of date, FSO 3.7.2 is also out of date. You should use 3.7.4 instead. Also, unless your CPU is positively ancient, it should support at least SSE2 and you can just use the standard builds instead of SSE ones.

[jr2]

Also, unless your CPU is positively ancient, it should support at least SSE2 and you can just use the standard builds instead of SSE ones.

This seems to come up a lot.  I wonder if *_SSE.exe should be renamed *_SSE_legacy.exe  People who have an understanding of what SSE is will be likely to choose the build that mentions it, not knowing that the standard build has SSE2 support.  It's like the previous problem we had (users not choosing SSE2 because they didn't know what it was), but in reverse: tech-savvy people choosing SSE because they know it's an optimization their CPU supports, not realizing FSO standard has SSE2 support.

EDIT: I take that back...


What would probably have been least confusing, would have been to label all non-SSE builds *_legacey.exe, and just do *_standard_SSE2.exe to show that this is the normal build to be using for most folks.

[Yarn]

What would probably have been least confusing, would have been to label all non-SSE builds *_legacey.exe, and just do *_standard_SSE2.exe to show that this is the normal build to be using for most folks.

In addition to something like that, I say discontinue the SSE builds. That would reduce clutter and make it unnecessary to directly reference SSE/SSE2 in build names. And the small number of players with CPUs that support SSE but not SSE2 would still be able to run the legacy (no-SSE) builds.