Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: Maddoxk6709 on February 28, 2013, 05:05:24 pm
-
Hi guys, I'm having a graphics issue in Shrouding the Light (Technically Origins but still).
For some reason the Aten and Anubis don't seem to have the mediavps applied. Everything else looks like it should.
At first I thought it was because I was using the latest release (3.6.12) mediavps rather than the ones that were available at the time (3.6.10? Whichever one had the folder as "mediavps" rather than "mediavps_3612". But I had the same issue with the earlier mediavps.
My mod.ini looks like this
[launcher]
image255x112 = STL.bmp;
infotext = A year has passed since the destruction of the Lucifer and the flight of the Shivan armada. In the year 2336, the Terran and Vasudan peoples attempt to reclaim their former empires and piece together their shattered lives. However, dissidents and splinter groups from within jeopardise their hopes of peace - fighting for independence or against hated alien foes. In the midst of all this turmoil, you are transferred, from the safety of the 1st Battlegroup of Vasuda to the 13th Battlegroup's PVD Guardian and the troubled hotspot of Deneb...;
website = http://mysite.wanadoo-members.co.uk/sbre/stl/stl.htm;
forum = http://www.hard-light.net/forums/index.php/board,39.0.html;
[multimod]
secondrylist = fsport,mediavps_3612;
What might I be doing wrong or what might be the issue? Thank you.
-
Did you try adding the fsport media vps to the list, unenabling the mod and re-enabling it, then trying again? Fsport mediavps have the HTL Anubis, as for the Aten I believe it might help but I'm not so sure. Try it and we'll see what happens.
-
I'll give that a shot, would I want my mod.ini to look like this?
[multimod]
secondarylist = fsport,fsport-mediavps,mediavps_3612;
-
I believe I got it to work. I tried adding the media-vps for fsport but it didn't change anything. I removed the fsport vps and kept the fsport-mediavps and it changed the models properly but threw up errors.
But! I added the fsport-mediavps as a primary list and the fsport files and 3.6.12 media vps as secondary and the fancy models are in now without any errors.
Thanks for the suggestion and help. :)
-
But! I added the fsport-mediavps as a primary list and the fsport files and 3.6.12 media vps as secondary and the fancy models are in now without any errors.
Yep, that sounds about right :)
-
I'm sorry for the bump, but I was having the same issue basically. The Vasudan installation looked 'normal' and gray and didn't have the blue lines on it that the fancier model has.
Is this what the mod.ini should look like:
[launcher]
image255x112 = STL.bmp;
infotext = A year has passed since the destruction of the Lucifer and the flight of the Shivan armada. In the year 2336, the Terran and Vasudan peoples attempt to reclaim their former empires and piece together their shattered lives. However, dissidents and splinter groups from within jeopardise their hopes of peace - fighting for independence or against hated alien foes. In the midst of all this turmoil, you are transferred, from the safety of the 1st Battlegroup of Vasuda to the 13th Battlegroup's PVD Guardian and the troubled hotspot of Deneb...;
website = http://mysite.wanadoo-members.co.uk/sbre/stl/stl.htm;
forum = http://www.hard-light.net/forums/index.php/board,39.0.html;
[multimod]
primarylist = fsport-mediavps
secondarylist = fsport, mediavps_3612;
I tried putting it like this (like was suggested). The appearance of the ships/installation looks like the 'fancy' models (as Maddox put it) but it says it encountered errors when starting up. Do I need to play it on a certain build? I don't know if it will make a difference, but I've attached a fs2 open log.
Some more info, if it helps: after the opening screen that said 18 errors were encountered I went into the game anyway. I played two missions through the techroom; in STL: Origins I played "At The Gates" (recapturing the installation/shipyard) and the mission "Siege" from STL proper. Both missions worked fine so hopefully if there are 'errors' in the game they're not game-breaking.
[attachment deleted by an evil time traveler]
-
Did I do things right?
-
weapons.tbl(line 3241): Warning: Error parsing id# in XSTR() tag XSTR(
"Infrared and ultraviolet tracking - designed to fire in small groups of 4 missiles per burst - light medium payload per missile (12 Kt) - semi-intelligent on-board tracking - single-pass kill probability will not exceed 60% on average -designed as an offensive version of the Fury. As a "swarm" based weapon, this missile can take out an unshielded fighter without any difficulty. It's four missile system almost guarantees one or two hits, and its speed is quite amazing. Twice as powerful against naked hulls.
The GTM-4 Hornet was showing its age even toward the end of the Great War, but it was cheap to manufacture. As a result, war-time production of the Hornet ran full-tilt at factories in eight star systems right up to the end of the war. After hostilities ceased, the GTVA found itself with an inventory of 2.6 million Hornet missiles. This stockpile has been spread among all GTVA battle groups, with each recieving at least 100,000 Hornets. This aspect-seeking missile still delivers a devestating four missile punch, which makes it a consistent favorite of many pilots.", 3328)
WARNING: "weapons.tbl(line 3241): Warning: Error parsing id# in XSTR() tag XSTR( "Infrared and ultraviolet tracking - designed to fire in small groups of 4 missiles per burst - light medium payload per missile (12 Kt) - semi-intelligent on-board tracking - single-pass kill probability will not exceed 60% on average -designed as an offensive version of the Fury. As a "swarm" based weapon, this missile can take out an unshielded fighter without any difficulty. It's four missile system almost guarantees one or two hits, and its speed is quite amazing. Twice as powerful against naked hulls. The GTM-4 Hornet was showing its age even toward the end of the Great War, but it was cheap to manufacture. As a result, war-time production of the Hornet ran full-tilt at factories in eight star systems right up to the end of the war. After hostilities ceased, the GTVA found itself with an inventory of 2.6 million Hornet missiles. This stockpile has been spread among all GTVA battle groups, with each recieving at least 100,000 Hornets. This aspect-seeking missile still delivers a devestating four missile punch, which makes it a consistent favorite of many pilots.", 3328)" at parselo.cpp:334
Int3(): From c:\code\fs2_open_3_7_0\code\globalincs\windebug.cpp at line 1378
Hmm, interesting... This could be the FSPort weapons.tbl. Have you tried using an older FSO build? The FSPort release thread says it was tested for FSO 3.6.18.
-
As far as I know Shrouding the Light has not been upgraded in a long time. I believe it has it's own ship and weapons table. This is probably what is causing the errors. It will not prevent the mod from playing.
-
As far as I know Shrouding the Light has not been upgraded in a long time. I believe it has it's own ship and weapons table. This is probably what is causing the errors. It will not prevent the mod from playing the mod.
So basically even though I see that error screen, I should be able to play the game?
-
Correct