init.sqs

[nominesine]

It seems that init.sqs isn't as fool proof in ArmA as it used to be in OFP, or am I imagining things? I did the following tests in init.sqs

Code: [Select]

hint "Test if init.sqs is working or not"I added that line to my init.sqs and started the mission several times. In 8 tries out of 20 the hint wasn't shown at startup. Has anyone else noticed that init.sqs is more unreliable then it used to be in the good old days?

EDIT: And while I'm on the subject... are all the other event based scripts that came with OFP still functioning the way they used to?

[LeeHunt]

Strange, maybe add a delay ~5 or something to give it time to kick in?

[Mandoble]

Well, as far as I know any hint needs display number 46 (ArmA main screen) to be created and present. In init.sqs if you try _disp = findDisplay 46 as first line the return will be null all the times, your 8 hints out of 20 is a miracle

I agree with Lee, sleep a second first and then execute your hint.

[Mr.Peanut]

The init is okay, but when it gets executed is variable, which is why your hint will not display all the time. A pause(of any time length) in your init will make it wait until the mission is actually started before executing the hint. In any event, the init is not the place for that. Call another script from your init, and put a small pause at the top of that script, then have your hint command.

[nominesine]

Just to clarify...

The problem i not really that I cannot add a hint command to the init.sqs. The real problem was a camerascripts that I wanted to execute right at the beginning from the init.sqs, using the following syntax:

Code: [Select]

[] exec "film.sqs"Sometimes it worked, sometimes it didn't. I threw in the hint for testing purposes only. The camerascript needs to be launched directly, hence a delay of ~00000.1 or whatever will not work. I can make a workaround and execute the script from the initline of the player unit. Though I would still prefer to find out if the init.sqs is reliable or not. Maybe it's a Windows Vista problem? If anyone can shed some light upon this matter I'd be grateful.

[Baddo]

Hi nominesine

I don't know if this works in ArmA or helps in your situation but I did this in a mission I made for OFP: I put a condition to wait until an airbourne vehicle had started moving and only then I let the script continue.

The check I used was:

Code: [Select]

@(speed BDO_uav > 0)
The reason I needed this was that I started a cutscene script from an initialization field of a UAV and I had a disableUserInput true in there... if I didn't put some conditional check into it then the user input was disabled for the briefing 

I think I had the conditional check in the init.sqs file too at some point in development and it worked okay from there too.

It worked fine in OFP. The UAV set to "flying" only starts to move after the briefing is over and the mission is started. The cutscene is showing view from the UAV right at the start of the mission and it worked perfectly. Maybe you can do something similar.

Best Regards,
Baddo.

[WhisperOFP]

Sorry to interfere, but isn't init.sqf/init.sqs launched during the mission briefing? In which case, you'd need to wait a bit more before launching the cutscene, wouldn't you?

[Mandoble]

Nope, init.sqs is launched when mission starts.

Investigation: Initialisation of units/objects/waypoints/triggers

Nominesine, so far init.sqs has been always reliable for me (including camera creation at the very beginning of init.sqs). Are you sure your camera script is 100% innocent of that problem?

[JasonO]

If the init.sqs file is launched when the mission starts, then how come things like objectives for the breifing when you want to hide them work from using objstatus in the init.sqs.

[Mandoble]

May be init.sqs is parsed first just looking for objStatus commands there.

[Mr.Peanut]

From that old article:

Init.sqs without a delay will be finished before starting the game in every case.

i.e. the init starts right after passing the slot selection screen and, supposedly, will always finish before the mission starts. A pause will halt script execution until the mission starts. So script out what you are doing and put a small pause at the top of that script. That way your init will continue to process, while your cam script waits.

[nominesine]

Are you sure your camera script is 100% innocent of that problem?

Yes I am. I think the failure to execute the simple hint command proves that it is not the scripting, its the init that causes the problem. I am, however, uncertain if this is fault of the game engine or my operating system (I installed Vista on my new computer, wich I sincerely regret).

[Mr.Peanut]

1) Remove all pauses from your init
2) Place a 0.5 pause at the very top of each script that requires it, your cam script in particular

This does not fix the problem?

Yes, installing Vista was a mistake as far as ArmA. Bi has officially stated that ArmA does not support Vista.

[nominesine]

Yes, installing Vista was a mistake as far as ArmA. Bi has officially stated that ArmA does not support Vista.

I know  But it least it was cheap 

I installed ArmA on my old compuiter, just to check what happened in XP. It worked like a charm (but ArmA is extremely laggy on my old computer). Maybe it's a hardwareproblem rather than an editing problem?!? That's a relief to me, because then I just have to wait for a better Windows Patch. I don't have very much time for scripting anymore, so Vista will probably be upgraded several times before I have anything ready for release 

[Mandoble]

May be you can do a dual boot Vista/Xp in your Vista computer.