Home   Help Search Login Register  

Author Topic: Mission functional in editor crashes when exported to single missions  (Read 599 times)

0 Members and 1 Guest are viewing this topic.

Ade

  • Guest
 :'(

I have a rather depressing problem.  I have an incomplete (haven't done the intro yet, and needs more work before beta testing) but functional single player mission.  It uses only three addons:

JAM 2
VIT_APC (various APC's and IFV's and some fixed weapons)
UCE_Rustaiga (Russian MVDs)

There's nothing particularly odd about the mission, apart from one thing that I will explain in a moment.  The only scripts it uses are General Barron's AI script and a very short camera script that is launched from a unit's init field.

I had the endings working OK in the editor and added decided to export it to my single mission folder to check that a clutch of extra (JAM) weapons that I added via the description.ext were all alright.

However, when the briefing screen appears, OFP locks up, although I can still Alt-Tab in and out.

The only oddity is that in the init.sqs I use removeAllWeapons / addWeapon to swap the UCE_Rustaiga retextured BIS weapons for JAM equivalents.  This seemed to work fine in the editor but I thought this might be the problem.  So I deleted the weapon changing part of the script and re-exported the mission with the new init.sqs, but the same crash happened, so it can't be that.

I've checked my spelling of classnames in description.ext and I'm sure it's not that.  I've also tested exporting other single missions and they all work fine.  I have OFP 1.96 and FDF 1.3.  The problem is the same whether I am running FDFMOD.exe or FLASHPOINTRESISTANCE.exe.

Can anyone help?  ???  ???  ???  I'm not keen on starting from scratch because I'm quite pleased with how the mission plays.

Ade

Offline Triggerhappy

  • Contributing Member
  • **
  • Llama, it's what's for dinner.
go through everything in your mission and check for things that may be wrong or anything like that, figure out a way to check them to see if they're the problem,say, by pulling them out of the folder and then starting it, and fix anything that may be questionable.
also, i've heard somewhere that if you have multiple folders in your mission folder, you need to use a specific slash (/ or \) for it to call/exec/whatever things in that folder...

don't know if that is very helpful, but i would do that

Offline macguba

  • Former Staff
  • ****
    • macguba's operation flashpoint page
Odd one.    It doesn't sound like a description.ext problem.  

What happens in the mission editor when you press the shift key while clicking Preview?

Does it lock up as soon as the Briefing starts, or when you click the Gear tab, or what?

« Last Edit: 13 Nov 2004, 23:50:50 by macguba »
Plenty of reviewed ArmA missions for you to play

Offline dmakatra

  • Members
  • *
  • Better known as Armsty
Hmmm... Try merging it with an empty map and save it under a new file name. If that doesn't work, try manually PBO it with MakePBO.

:beat: *Gets Shot* :beat:

Offline Triggerhappy

  • Contributing Member
  • **
  • Llama, it's what's for dinner.
@Macguba

ahh... somebody didn't read the whole post...  :P

...working OK in the editor...

...or the name of the thread
Mission functional in editor crashes when exported to single missions
 ;D
« Last Edit: 14 Nov 2004, 00:53:04 by Triggerhappy »

Ade

  • Guest
Cheers for the help chaps, I think I've cracked it!  :D

In the little camera script, I put a disableUser Input = true, and cancelled it just before the exit command.

But the script is called from a unit's init field to make sure it kicks off straight away.

So user input was disabled at the briefing.  Seems OK now, but that's one to remember - maybe stick it in the FAQ section.  One day I may just get the hang of this...  ;)

Ade