[Striker]

I have a problem. I put everything under ShroudingTheLight (folder), with all data in its right place, and set SCP to read from that mod folder. But every time I try the first actual mission, I have a Ulysses and no weapons with no choices. I cant even begin the mission. Help.

[karajorma]

Go into ShroudingTheLight/Data/tables/ and delete (or rename the extensions of) the ships and weapons tables. These are the Lightspeeds tables and they're overriding the ones Blaise made in the vp.

Do NOT delete the weapons explosions table.

[Lightspeed]

Do you have the FS1port installed in the MOD directory?

THAT might be your problem.

[karajorma]

Actually I think it's your tables LS.

The FS Port VP comes after the StL VP in the alphabet so Blaise's tables will superceed those unless someone installs tables in the data folder (or they've cocked up the install somehow). Since your weapons don't come in a VP people will probably just install them to the data folder.

Simple fact is that I had exactly the same error as Striker and deleting those two tables cured it.

[Kosh]

I actually never had that problem. Wierd.

[Akalabeth Angel]

I never had that problem because I didn't extract the table that came with the nebula backgrounds. Of course I had the problem of SCP being too hot to handle for my pooter.

[InfernoGod]

I just finished the campaign, and all I can say is wow. The plot was, well, to admit, a little slow at first, but at the third mission it just picked up speed. I enjoyed this campaign. I'd say something in Vasudan, but I'm still on the GTVA Alien Language waiting list... anyway *holds up sign* . oh- that should say 10...

[Trivial Psychic]

Well I'm partway through this campaign, and now that the intriegue is picking up, its realy starting to get interesting.  I was blown away (not exactly literally) by the arrival of those... new HoL bombers.  It was a plot twist I had not seen coming.  Things I find frustrating but not necessarily bad with this campaign so far include:

1 - Anibus sux!  I keep wanting to hit my burners but they're never there.

2 - Trying to shoot down those tiny Barracudas being launched by waves of Seths is quite irritating.

3 - Not being able to use weapons like the PromS or Interceptor (at first).  I guess that Alpha 1 from the original Great War campaign was just a fortunate pilot that got to use the latest toys as they came out.  Of course, it could be worse... I could be trying to fight with the VLL-9.

4 - The memory-hogging of Lightspeed's Uber Nebulae, which eat up memory and sometimes force me to reboot between missions (shouldn't be happening on AMD-XP2600, 512DDR-400, ATI R9600XT).

Oh well, I'm curious to see what happens next.  I just passed the operative insertion mission.

Later!

[Black Wolf]

Originally posted by Trivial Psychic

4 - The memory-hogging of Lightspeed's Uber Nebulae, which eat up memory and sometimes force me to reboot between missions (shouldn't be happening on AMD-XP2600, 512DDR-400, ATI R9600XT).

Make sure you're using a post memory leak fix build, which I think means post 3.6 as well, but I'm not absolutely certain. I'm using what I think is taylors latest build (fs2_open_T-20040822.exe), and it's remarkably stable and very memory friendly.

Also, if they're still a problem, use the 256 colour pcx versions. There's some quality loss, but it's really only noticable in screenshots or when you're looking for it, and the memory saving is huge.

[Trivial Psychic]

I'll try that.  Thanx.

[NGTM-1R]

God knows how many times I've tried to hit my burners in the Anubis and found there was nothing there. I know it's killed me at least twice...

[Lightspeed]

'kay kay, I feel I need to comment

Originally posted by Trivial Psychic
Things I find frustrating but not necessarily bad with this campaign so far include:

1 - Anibus sux!  I keep wanting to hit my burners but they're never there.

2 - Trying to shoot down those tiny Barracudas being launched by waves of Seths is quite irritating.

3 - Not being able to use weapons like the PromS or Interceptor (at first).  I guess that Alpha 1 from the original Great War campaign was just a fortunate pilot that got to use the latest toys as they came out.  Of course, it could be worse... I could be trying to fight with the VLL-9.

4 - The memory-hogging of Lightspeed's Uber Nebulae, which eat up memory and sometimes force me to reboot between missions (shouldn't be happening on AMD-XP2600, 512DDR-400, ATI R9600XT).

Oh well, I'm curious to see what happens next.  I just passed the operative insertion mission.

Later!

1- It's Anubis. And it doesnt suck - it's fun!!

2- They're deliberately hard to shoot down since it's missiles, not bombs. High hit chance at mediocre damage.

3- Prometheus guns (the original, NOT the S version, which is a derivate from the original but still different) are VERY rare, because resources are lacking (untill FS2's nebula missions), so they probably still got most of them left (as its shortly after FS1), but save them for very special missions/objective, since they practically cannot be rebuilt.

4- They shouldn't cause that. I'm myself only having 512 MB of RAM, and have no problems whatsoever with the nebulae. Bob has optimized the nebula background rendering and ever since that, they are no real source of slow-down.

Originally posted by Black Wolf

Also, if they're still a problem, use the 256 colour pcx versions. There's some quality loss, but it's really only noticable in screenshots or when you're looking for it, and the memory saving is huge.

This will not really help things, I'm afraid. The memory saving is ONLY there if you don't use "-pcx32" (else it'll fill EXACTLY the same size), the visual quality is significantly worse.  Performance wise, there is little or no difference (tested that).

[Black Wolf]

Originally posted by Lightspeed

This will not really help things, I'm afraid. The memory saving is ONLY there if you don't use "-pcx32" (else it'll fill EXACTLY the same size), the visual quality is significantly worse.  Performance wise, there is little or no difference (tested that).

Hence why those of us without super high end systems don't use pcx32.

[Trivial Psychic]

I don't use -pcx32.  Perhaps switching to the pcx nebulae and using -pcx2dds will improve matters.

[Kosh]

4 - The memory-hogging of Lightspeed's Uber Nebulae, which eat up memory and sometimes force me to reboot between missions (shouldn't be happening on AMD-XP2600, 512DDR-400, ATI R9600XT).

My system at home is much crappier (and older) but it appearently works better.

[Trivial Psychic]

Well, something about STL is realy eating up the memory, as the FS2 main campaign has no problems with me flying 3 or more missions.

[Kosh]

Btw, what flags are you using?



EDIT: I just had a thought: What I did with my system at home was use the lite version of mveffects, but added explosions, lightspeeds nebula's and his weapon effects onto it. It won't look as good, but it is quite playable.

[ARSPR]

I have just instaled this mod and I think something must be tuned up to work right with vp 3.6.8 Delta.

The problem is caused with LS Weapons Pack (link in first page of the thread). I have noticed than in BR's webpage there's no reference to this pack so I tried with and without it.

Without it

Just before finishing the load of first mission (the cutscene) the next error appears

Code: [Select]

Error: Can't open model file <none>
File:\fs2_open\code\model\modelread.cpp
Line: 1748
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
But if you press OK the game seems to work fine (I have passed two real missions).

With it

I've built a vp with the link contents named 00-WeaponsPack.vp (to make it load before the MOD itself) and I have put it inside the MOD directory. With the mod.ini file, FSPort and Nebula backgrounds are also loaded from their own directories.

With this pack the previous error doesn't appear but all the ships are turned into Ulysses. And as you can see in weapon selection window from the first real mission, there's no available weapons. (I attach a screenshot).



So, if I haven't made anything wrong, I think there's some kind of issue with newest media vps.


[attachment deleted by admin]

[Blaise Russel]

I've built a vp with the link contents named 00-WeaponsPack.vp (to make it load before the MOD itself) and I have put it inside the MOD directory. With the mod.ini file, FSPort and Nebula backgrounds are also loaded from their own directories.

With this pack the previous error doesn't appear but all the ships are turned into Ulysses. And as you can see in weapon selection window from the first real mission, there's no available weapons. (I attach a screenshot).

This is probably the problem right here. I guess that 00-WeaponsPack.vp has table files in it; in which case, since you're giving it priority over STL, it's messing everything up because the missions are referencing STL weapons and STL ships from the STL table which is being overwritten by your 00-WeaponsPack tables.

Try renaming it to just WeaponsPack; that way, FS2 can still access the weapons effects in the VP, but it'll use the STL tables so the campaign should work.

[ARSPR]

This is probably the problem right here. I guess that 00-WeaponsPack.vp has table files in it; in which case, since you're giving it priority over STL, it's messing everything up because the missions are referencing STL weapons and STL ships from the STL table which is being overwritten by your 00-WeaponsPack tables.

Try renaming it to just WeaponsPack; that way, FS2 can still access the weapons effects in the VP, but it'll use the STL tables so the campaign should work.

Thank you, Blaise. Now it works perfect. And yes the WeaponsPack has three tables: ships.tbl, weapon_expl.tbl and weapons.tbl

PS. If the weapons pack is needed, as it seems, you should update your webpage to include it (and maybe make an vp with it so it doesn't cause this priority error).