Global Mission options

[graywo1fg]

Having a problem here and i have read the GUI manual in the Mission Options and all..... here is my problem........ when in the mission editor, i want to set it so i have external views ON!! but i want PADLOCK off.... and so in the mission options in the editor i specify that with both check marks by external views, and only the left check mark by padlock....... and on my server for multiplayer, i have in my main options menu "Use these options for every mission" UNCHECKED! so it should use the mission option to have external views but no pad lock view.... however when i load into the mission as a client... i get external views, good.... but Pad Lock still works?!?!?!?! now on my server i have made sure the mission options are right and saved and re-saved them time and time again i have tried with my main options as checked to use in every missions and tried every combination...... so my question is........ If external views are on, is padlock always on? and is pad lock even a value that works in the mission options?:huh: or maybe possibly does the server need to join a KA-50 slot to force these options instead of staying in spectator?

Edited March 14, 2009 by graywo1fg

[graywo1fg]

Cough cough :P

[graywo1fg]

does anyone know? :(

[graywo1fg]

is this "global devs ignore graywolf" month? :P

[JG14_Smil]

never build missions using the global settings in BS options. if you build a mission that others will fly, your settings will over-write who ever plays the missions. So, the person who made the missions you are flying probably had the "use these settings in all missions' checked in their settings - they are different than what you like, but you cannot change their settings to your liking as they are not checked when you try to edit the mission options. it is kind of cheesy.

 

if you are talking MP missions, that is different as some don't want external or padlocking on and that is normal..

Edited March 15, 2009 by JG14_Smil

[graywo1fg]

you dont understand what i am saying..... it is I making the missions and playing them online with my squad and i'm trying to have external views but no padlock and i have tried many diff combination's of mission options and regular options to try to get the right outcome but it never works. i have tried "use settings in all missions" both checked and unchecked and i'm wondering if its a bug where it doesnt matter if externals are on because if they are that means pad lock will be on....... get me? :P lol confuses me too

[EvilBivol-1]

I just did a test with GrayGhost and it seems to have worked fine. It sounds like you're doing it correctly though, so I'm not sure what's going on.

 

To reiterate, the server can enforce game options by checking the "ENFORCE" check boxes in the mission options. If you want the option enforced ON, you also check the VALUE box on the right. If you want the option forced OFF, you leave the VALUE box to the right unchecked. The server also needs to uncheck the "use these options for all missions" box in his GAMEPLAY options prior to starting the server.

Edited March 15, 2009 by EvilBivol-1

[graywo1fg]

yup roger :) thanks for testing...... the interesting thing is that when i made my missions i did it on my game computer then i transfered the missions over to my server through the LAN and after i did that the mission options i had set when building the mission did not take place until i went in on my server and re-saved the missions :P wierd. So you guys were able to have pad lock off and still have externals ?

[Distiler]

There is still something weird in all this.

 

I check force external view to all misions through global game options (use these options for any mission). I don't even touch any mission options switch.

 

I hit play mission from the editor. Works fine, externals are on. It seems the game created a mission in /temp folder using global settings. Cool.

 

I start multiplayer mode and start a local server from whre I play. Externals are disabled. Something is wrong. There is not any file in /temp folder, it seems using the original file.

 

Both options file in .miz and /scripts/options.lua show:

 

setGlobal = true

 

and while the first show externalViews = false the second shows externalViews = true (as it should be).

 

Why is it picking the options (in the .miz file) if in the same file it says setGlobal = true and /scripts/options.lua show externalViews=true?

 

 

 

Perhaps part of the fishy thing is in the options in .miz file. If I create the mission using (or not) global game options (use these options for any missions) it will stay setGlobal = true/false no matter what I do, so if I give the mission to a server that doesen't have that option activated/deactivated, it will work as if it is/isn't.

Perhaps missions should be done without the global game options in game options menu so they carry the tag setGlobal = false?

 

I'm really confused! I understand global options in sp missions but not in mp missions. Why is it working different? or is it because I test them in a local server? what I just want is the same settings for all the mp missions, regardless how have those been created.

Edited April 7, 2009 by Distiler

[Distiler]

ok, I think part of the bug is related to the fact that forcing global settings and re-saving a mission with custom settings, changes the mission.miz/option file but the check boxes in the editor don't update.

 

Example: if I have a mission with external view check box active in the editor and I re-save it using no-externals as a global settings, the editor still will show externals enabled but internally, the mission file will say externalViews = false.