Problem with Texas System
-
The quickfix doesn’t work… another ideas?
-
That’s pop zone not patrol route. Save your mod to another location, then delete all patrol routes near the jgs and watch what happens. Anyway pop zones don’t usually make crashes but npc appearance problems.
Meanwhile check npc loadouts with FL error checker. -
Could be related to a loadout for the NPCs, or even an altered pilot or formation.
Although, I believe missing pilots and incorrect formations usually just result in the NPCs not showing up at all.
I wonder…
Do NPCs have to have encounters on both sides of the jumphole? Would that cause a problem if an NPC encounter on the New York side didn’t exist on the Texas side? Especially if the NPCs actually use the hole? -
So there is another problem… I’m just searching what could it be.
-
Hey I’ve an idea! If it was the voices the problem that cause it. At the end of the spew, there is some voices error. So if I replace SDK 1.5 voice_properties.ini by the SDK 1.3 one it could work. Try it now!
Edit : That wasn’t that…. -_-’
-
So is there no other solutions?
-
The only thing I can say is flmod your changes up and attach it / upload it somewhere, then if someone else experiences the same crash it’s down to the changes, if they do not its down to your hardware / software configuration.
That might provide clues as to where the issue actually is rather than us taking stabs in the dark.
-
OK I upload in this web site.
-
Upload to GameFront done, I sayd I’ll upload there but that’s less securised beacause I use Realistic Lighting. My mod revamped
-
Aproximatly… I’ve put HQ textures on it, so that’s realy big.
-
Aproximatly… I’m an HQ fan.
-
that code referenced at the bottom of page 1 is not the system.ini for texas system… it’s for a jumpgate (or jumphole) leading to NY from Texas and should be just one of many nickname segments from the texas system.ini.
However, since the same happens when trying to jump to california system, I’d lean towards objects or NPC issues. Look at the top of each system.ini and you’ll see where the encounters call up their respective .ini’s. Look at both texas and california system.ini’s and omit (use a ; before the line) any encounters that are common/shared in both system.ini’s.
-
Nothing like what you say, it always bug.
