Are you feeling lonely or just plain horny then Click Here!!! and you'll have lots of fun...
Important MessageYou are browsing the archived Lancers Reactor forums. You cannot register or login. |
**Tutorial** - Find answers to crashes!
Here you find the different tutorials on editing and MODing Freelancer
61 posts
• Page 2 of 5 • 1, 2, 3, 4, 5
that's good i never new it till now. Thanks for the tip
Are you feeling lonely or just plain horny then Click Here!!! and you'll have lots of fun...
Are you feeling lonely or just plain horny then Click Here!!! and you'll have lots of fun...
Like the tip - nice stuff. Usually i just go into EXE folder, right click and use send to desktop. However, doing it manually is definately something that i wanted to know about, so no laughing here!
Are there any other sections, as honestly only systems really has typical repeated mistakes in over and over again. the rest is just spelling, checking that the references to other files is correct and stuff. that is about it, only systems really has these stereotypical problems!
If you do though, ask away, and i will answer when i notice (that something new has been posted! LOL). If you need help - then the newbie questions look no further threads by Accushot and myself are in general modding forum!
BUT - check SPELLING (loadouts is a major spelling cockup area!)
CHECK REFERENCES: - like new weapons and so on, nicknames correct? IDS numbers correct etc etc
Are there any other sections, as honestly only systems really has typical repeated mistakes in over and over again. the rest is just spelling, checking that the references to other files is correct and stuff. that is about it, only systems really has these stereotypical problems!
If you do though, ask away, and i will answer when i notice (that something new has been posted! LOL). If you need help - then the newbie questions look no further threads by Accushot and myself are in general modding forum!
BUT - check SPELLING (loadouts is a major spelling cockup area!)
CHECK REFERENCES: - like new weapons and so on, nicknames correct? IDS numbers correct etc etc
Ths is a problem youvealleready covered "game crashes when you launch from start planet and goes to desktop" i havent done any of the errors you said like overlapping gates, i used Freelancer Explorer to add a jump gate to Alaska and it doesnt turn up and i added 2 trade lanes that i somehow cant see (i worked all this out from freelancer explorer so i dont know if they are in the real game or not cuz it dont work!!)
-Trail-
[email protected]
-Trail-
[email protected]
oh yes, bewareth of adding objects to manhatten, for the game gets disturbeth and die.
I once built a nice little tradelane taking 40k up from manhatten. Lovely it was, lovely, but every time i got to the other end, i crashed.
I added nothing but the tradelanes at all - so no encounters etc, and it crashed.
Now, i was informed by Giskard that u can only have a certain amount of things in a system before the old ones disappear.
ALso - there is a finite of 8 jumpholes etc too apparently. So - it might be putting in too many things to one system, it could be the extra jumpgate giving it a fit.
Those are just for starters. It also could be that the trade lanes are numbered incorrectly - like li01_tradelane_gate_12 which is making two of those tradelanes, but this not only occurs in the actual tradelane name, but also in the goto function - if it is the same as another. That causes crash to desktop on launching from a planet. Now - when adding multiple things, best thing to do, remove the tradelanes - see if your still crashing (you shouldn't be) but be careful where you have added things. Next, add one tradelane and see if you crash. Then add the second one. If you crash, it is that tradelane - give it a thorough checking out, make sure its all there.
Also - how many have you added. If you have put in too many objects, like Giskard said, things start disappaering. If something that is necessary for the storyline disappears, then the game will die - no matter what you try it will kark it. Unless you do some massive changes to the the freelancer.ini file i think it is (has a check these files function i think)
Have a go at those, then find which is causing the crash. IF you still cannot find the prob - then post the troubling thing (like tradelane stretch) up here, and will have a peek for you
However, as Giskard said, stay away from Manhatten when modding objects and you should be fine. It is very very pissy in manhatten.
I once built a nice little tradelane taking 40k up from manhatten. Lovely it was, lovely, but every time i got to the other end, i crashed.
I added nothing but the tradelanes at all - so no encounters etc, and it crashed.
Now, i was informed by Giskard that u can only have a certain amount of things in a system before the old ones disappear.
ALso - there is a finite of 8 jumpholes etc too apparently. So - it might be putting in too many things to one system, it could be the extra jumpgate giving it a fit.
Those are just for starters. It also could be that the trade lanes are numbered incorrectly - like li01_tradelane_gate_12 which is making two of those tradelanes, but this not only occurs in the actual tradelane name, but also in the goto function - if it is the same as another. That causes crash to desktop on launching from a planet. Now - when adding multiple things, best thing to do, remove the tradelanes - see if your still crashing (you shouldn't be) but be careful where you have added things. Next, add one tradelane and see if you crash. Then add the second one. If you crash, it is that tradelane - give it a thorough checking out, make sure its all there.
Also - how many have you added. If you have put in too many objects, like Giskard said, things start disappaering. If something that is necessary for the storyline disappears, then the game will die - no matter what you try it will kark it. Unless you do some massive changes to the the freelancer.ini file i think it is (has a check these files function i think)
Have a go at those, then find which is causing the crash. IF you still cannot find the prob - then post the troubling thing (like tradelane stretch) up here, and will have a peek for you
However, as Giskard said, stay away from Manhatten when modding objects and you should be fine. It is very very pissy in manhatten.
C:\Documents and Settings\Zerocyde\Local Settings\Application Data\Freelancer\FLSpew.txt
This is the same output as the error log in the freelancer exe folder. The only thing I am not sure of is the logging level in that file, the usual error log in the exe folder does not show all errors because the freelancer.ini is not set to do that.
Primary Developer of the =EOA= Players Consortium
I am making NPC ships and the crashes are getting to me:
Okay - here goes.
When making ships for NPC's - we will start on fighters.
First - the ship has to be in the shiparch.ini correct? Good.
Next - You need a loadout of the ship in the loadouts.ini - follow the same methodology as the others, giving it your own nickname.
next - add this to the NPCships.ini file - as done in the others, finally plonk it in the faction_props.ini file as well (see other threads about this)
Okay - I crash whenever i am in a system. It can be many systems or not. It is NOT always the same location for crashes, it varies, and sometimes i can land sometimes i cannot.
Now this is stereotypical NPC crashes. Anything where you can get into the system, and see it, but crash all over the place = NPC's - so some poeple miss the obvious.
Rule:
1) Don't take any of them out of the faction_prop.ini file unless you really know what you are doing okay? Best to just add yours in there.
2) MAKE SURE you have them correctly labelled. So it says npcship = the nickname of the entry in npcships.ini (both these files are in the missions folder by the way).
3) MAKE SURE the archetype in both instances is the EXACT name of the ship in the shiparch.ini file okay??!!
4) make SURE the loadouts name is correct.
5) Make SURE the loadout corresponds to the ships hardpoints. Don't try giving it 200 lights or something stupid okay? ALso - make sure you give it an engine, powerplant and scanner at least! I mean, i forgot the engine once, couldn't stop laughing as all the corsairs sat in space without moving. Very comical stuff....hehe
6) Make SURE you have got the difficulty levels correct, and the type of ship correct okay?
Simple errors:
Copying the loadout from the goods.ini file instead to save time. Please remember to rename it to [loadout instead of leaving it as [good, also remember that in the loadouts.ini it is archetype - not ship, or hull or something. It should be the nickname, the archetype (ship nickname from shiparch.ini) and then the equip = lines.
Other probs - incorrect difficulty levels. Heck - make it d5 then make the nickname include it too, as well as the last line in the npcship.ini file. Why? Cause it keeps it simple, and uncomplicated. Specially when making multiple loadouts for different difficulty levels.
Checklist:
Shiparch.ini entry.
Loadouts.ini entry - same as other ones but tailor made to your ship, and also make sure the archetype is the shiparch.ini nickname for the ship.
NPCships.ini - now make sure the loadout is for your ship, that the archetype is the shiparch.ini nickname, that the shipclass is fighter, the level is the level you want, and that the npc_class = lawful, class_fighter, d7 line varies for lawful/unlawful for your good guys/pirate line.
Next - make sure the nickname of this part corresponds to the entry name for the faction_prop.ini file - like this:
I have the starblazer, i have a loadout for it (cannot be arsed to put it in here though) here are the others.
[NPCShipArch
nickname = starblazer_fighter_d5
level = d5
loadout = starblazer_loadout
ship_archetype = starblazer
state_graph = FIGHTER
pilot = pilot_company_hard
npc_class = lawful, class_fighter, d5
[NPCShipArch
nickname = starblazer_fighter_d7
level = d7
loadout = starblazer_loadout01
ship_archetype = starblazer
state_graph = FIGHTER
pilot = pilot_company_hard
npc_class = lawful, class_fighter, d7
And the faction_prop.ini file is:
npc_ship = starblazer_fighter_d5
npc_ship = co_alg_ge_fighter2_d6
npc_ship = co_alg_ge_fighter2_d7
npc_ship = starblazer_fighter_d7
I also add lines into the mshipprops too - this is incase i shove them into the missions later and i forget to do it!! Simple eh?
[mShipProps
archetype_id = starblazer
prop = can_use_berths
Dunno why i added this part really. I thought of others, but stuff like commodities, weapons, and even ships don't have that many crashes at all - they are mainly typos, whereas with systems you have a FLE that makes incorrect things for you, and a load of tutorials that are full of mistakes that newbs won't notice. Heck - there are hundreds of things causing crashes in systems, whereas everything else is much much simpler! lol. Hence why i haven't written about anything else - there aint much to write about. NPC ships can be buggy, but only if you forget or simply mis=spell something.
Everythign else is near plain sailing - so i won't add anything to this thread as - well, its not difficult to debug problems yourself. Only systems really stumps people! lol
Chips
Okay - here goes.
When making ships for NPC's - we will start on fighters.
First - the ship has to be in the shiparch.ini correct? Good.
Next - You need a loadout of the ship in the loadouts.ini - follow the same methodology as the others, giving it your own nickname.
next - add this to the NPCships.ini file - as done in the others, finally plonk it in the faction_props.ini file as well (see other threads about this)
Okay - I crash whenever i am in a system. It can be many systems or not. It is NOT always the same location for crashes, it varies, and sometimes i can land sometimes i cannot.
Now this is stereotypical NPC crashes. Anything where you can get into the system, and see it, but crash all over the place = NPC's - so some poeple miss the obvious.
Rule:
1) Don't take any of them out of the faction_prop.ini file unless you really know what you are doing okay? Best to just add yours in there.
2) MAKE SURE you have them correctly labelled. So it says npcship = the nickname of the entry in npcships.ini (both these files are in the missions folder by the way).
3) MAKE SURE the archetype in both instances is the EXACT name of the ship in the shiparch.ini file okay??!!
4) make SURE the loadouts name is correct.
5) Make SURE the loadout corresponds to the ships hardpoints. Don't try giving it 200 lights or something stupid okay? ALso - make sure you give it an engine, powerplant and scanner at least! I mean, i forgot the engine once, couldn't stop laughing as all the corsairs sat in space without moving. Very comical stuff....hehe
6) Make SURE you have got the difficulty levels correct, and the type of ship correct okay?
Simple errors:
Copying the loadout from the goods.ini file instead to save time. Please remember to rename it to [loadout instead of leaving it as [good, also remember that in the loadouts.ini it is archetype - not ship, or hull or something. It should be the nickname, the archetype (ship nickname from shiparch.ini) and then the equip = lines.
Other probs - incorrect difficulty levels. Heck - make it d5 then make the nickname include it too, as well as the last line in the npcship.ini file. Why? Cause it keeps it simple, and uncomplicated. Specially when making multiple loadouts for different difficulty levels.
Checklist:
Shiparch.ini entry.
Loadouts.ini entry - same as other ones but tailor made to your ship, and also make sure the archetype is the shiparch.ini nickname for the ship.
NPCships.ini - now make sure the loadout is for your ship, that the archetype is the shiparch.ini nickname, that the shipclass is fighter, the level is the level you want, and that the npc_class = lawful, class_fighter, d7 line varies for lawful/unlawful for your good guys/pirate line.
Next - make sure the nickname of this part corresponds to the entry name for the faction_prop.ini file - like this:
I have the starblazer, i have a loadout for it (cannot be arsed to put it in here though) here are the others.
[NPCShipArch
nickname = starblazer_fighter_d5
level = d5
loadout = starblazer_loadout
ship_archetype = starblazer
state_graph = FIGHTER
pilot = pilot_company_hard
npc_class = lawful, class_fighter, d5
[NPCShipArch
nickname = starblazer_fighter_d7
level = d7
loadout = starblazer_loadout01
ship_archetype = starblazer
state_graph = FIGHTER
pilot = pilot_company_hard
npc_class = lawful, class_fighter, d7
And the faction_prop.ini file is:
npc_ship = starblazer_fighter_d5
npc_ship = co_alg_ge_fighter2_d6
npc_ship = co_alg_ge_fighter2_d7
npc_ship = starblazer_fighter_d7
I also add lines into the mshipprops too - this is incase i shove them into the missions later and i forget to do it!! Simple eh?
[mShipProps
archetype_id = starblazer
prop = can_use_berths
Dunno why i added this part really. I thought of others, but stuff like commodities, weapons, and even ships don't have that many crashes at all - they are mainly typos, whereas with systems you have a FLE that makes incorrect things for you, and a load of tutorials that are full of mistakes that newbs won't notice. Heck - there are hundreds of things causing crashes in systems, whereas everything else is much much simpler! lol. Hence why i haven't written about anything else - there aint much to write about. NPC ships can be buggy, but only if you forget or simply mis=spell something.
Everythign else is near plain sailing - so i won't add anything to this thread as - well, its not difficult to debug problems yourself. Only systems really stumps people! lol
Chips
Walkin you through would take alot, however, have you tried this without server first, you gotta make sure it works.
Next - you crash on loading? Not even get to menu, or you get there, just trying to get somewhere else?
Reason server crashes, as it is running the encounters and other scripting (not all) from your server files, and then the game you load is running itself MINUS all server files - as it takes that info from the servers. So - server crashes point towards things like bad encounters and such like.
Where are you trying to start?
Personally - check in SP without server. Use an OpenSP program - do you land on manhatten without crashing, or do you crash on loading? Check the universe.ini file - anything visibly wrong, check systems files - anything wrong (might be if you modded manhat system), have you removed stuff, have you added stuff, what did you do exactly?. It is extremely difficult to work out what is wrong from a 'i crash on loading' kinda message. I take it that it all works perfectly when not running the mod at all?
I would look, but with a job,lots of mods etc etc, i have no time left. I also mean no time - i get about 2 hours a day of my own time right now, and that time is precious. However, if it comes to w/kend and it aint fixed, then i will have a look for you.
Chips
Next - you crash on loading? Not even get to menu, or you get there, just trying to get somewhere else?
Reason server crashes, as it is running the encounters and other scripting (not all) from your server files, and then the game you load is running itself MINUS all server files - as it takes that info from the servers. So - server crashes point towards things like bad encounters and such like.
Where are you trying to start?
Personally - check in SP without server. Use an OpenSP program - do you land on manhatten without crashing, or do you crash on loading? Check the universe.ini file - anything visibly wrong, check systems files - anything wrong (might be if you modded manhat system), have you removed stuff, have you added stuff, what did you do exactly?. It is extremely difficult to work out what is wrong from a 'i crash on loading' kinda message. I take it that it all works perfectly when not running the mod at all?
I would look, but with a job,lots of mods etc etc, i have no time left. I also mean no time - i get about 2 hours a day of my own time right now, and that time is precious. However, if it comes to w/kend and it aint fixed, then i will have a look for you.
Chips
i found out wat was wrong with my FLE crashing faluty systmes wouldnt open the file so i just deleted it.
i made two sytems mabey 1 encounter in 1 of the systems about 6 bases in total in both. meaning 4 bases in 1 and 2 in the other. the systems r full of wepons platforms. ther are two clouds in 1 of the systems and some caustion bouies.
i made everything sellable at 1 base(to see if it would wat all the guns did) and all the ships and guns and pattorls were highes lvl.
thats all pretty much. might be a few things that are i missed.
FYI i couldnt get to chose my char. i tried to log on and it crashed.
post bck soon.
i made two sytems mabey 1 encounter in 1 of the systems about 6 bases in total in both. meaning 4 bases in 1 and 2 in the other. the systems r full of wepons platforms. ther are two clouds in 1 of the systems and some caustion bouies.
i made everything sellable at 1 base(to see if it would wat all the guns did) and all the ships and guns and pattorls were highes lvl.
thats all pretty much. might be a few things that are i missed.
FYI i couldnt get to chose my char. i tried to log on and it crashed.
post bck soon.
went to bar? Hmm - usually means that there is an error in the base file of that base. Something like it doesn't have a bar, or something isn't right about it. Usually if you click on someething and you crash, then its that thing that is making you crash - therefore look there! Try the base file as well as the bar file too. Check the links to rooms etc.
Systems can crash for litterally thousands of reasons though - mostly related. 90% are encounters problems being wrong. Giving a wrong encounter or patrol path using these things is impossible to work out. Yes - patrol paths don't seem to work too well - but don't worry, patrols are crap anyways. Like i mentioned before though - there are multitudes of probs that can go wrong. Go through the list and really look. Spelling mistakes also cause crashes, especially when as un-noticable as in weapons files or something - that is hard to spot!!
Systems can crash for litterally thousands of reasons though - mostly related. 90% are encounters problems being wrong. Giving a wrong encounter or patrol path using these things is impossible to work out. Yes - patrol paths don't seem to work too well - but don't worry, patrols are crap anyways. Like i mentioned before though - there are multitudes of probs that can go wrong. Go through the list and really look. Spelling mistakes also cause crashes, especially when as un-noticable as in weapons files or something - that is hard to spot!!
61 posts
• Page 2 of 5 • 1, 2, 3, 4, 5
Return to Freelancer Editing Tutorial Forum