How to prevent user-made missions from using creator's snapviews?

[GregP]

This is an annoyance that's been around since the betas. It seems that the vast majority of user-made missions that I download somehow preempt my own snapviews and default viewpoints with (I'm guessing) whatever the creator was using. So for example my own tweaked HUD view now gets replaced with some other HUD view, apparently the one used by the mission designer.

 

It also seems that axis and button assignments are also prone to being preempted by user-made missions ... what's going on here?

 

Is there any way to prevent this from happening? It essentially makes these missions unplayable, doesn't it?

Edited February 23, 2012 by GregP

[Speed]

This is an annoyance that's been around since the betas. It seems that the vast majority of user-made missions that I download somehow preempt my own snapviews and default viewpoints with (I'm guessing) whatever the creator was using. So for example my own tweaked HUD view now gets replaced with some other HUD view, apparently the one used by the mission designer.

 

It also seems that axis and button assignments are also prone to being preempted by user-made missions ... what the hell is going on here?

 

Is there any way to prevent this from happening? It essentially makes these missions unplayable, doesn't it?

 

 

Honestly, I'm not sure what snapviews are (sadly that's true, though I have seen/heard them discussed frequently on the forums and over Teamspeak). You can press some kind of button and have your view snap to a location?

 

ANYWAY, this sounds like another instance of the unintentional (or otherwise) creation of a view.lua (or is it View.lua?) file inside the compressed .miz file. Unzip a .miz file, and look to see what's in it. IIRC, the only things that are essential to the mission is the "mission" file, any sound files, and any picture files. Everything else can go. I don't think we're to the point where we need warehouses.lua yet, that will be part of the upcoming resource management system, supposedly, but it's... upcoming :)

[Nate--IRL--]

Open the MIZ file in WinRAR or similar and delete SnapViews.lua and/or all LUA files.

 

Nate

[Shootist]

I know what he means. Cockpit views and MFD views. Ya, Ive seen that before. Easiest way is just to shrug it off.

[GregP]

OK so, removing all the *view*.lua files does indeed restore my desired modified snapviews.

 

HOWEVER, I can find no way to stop my controls from being remapped ... even if I delete every single file other than 'mission', still my controls are messed up. In a simple takeoff mission that I created long ago, my controls work fine. But as soon as I load another mission, suddenly roll and pitch are reversed and get 'stuck' in either full forward/backward/left/right after I move the stick.

 

Is this not a common problem? You guys can just take other people's missions and jump right in?

[PeterP]

Please post these mission files where you experience this behaviour.

A) Post the the unedited orginal mission

B) Post the mission after you have edited (deleted) the files inside

C) try to set up a similar missions with the same start

conditions.

 

D) post your complete view folder. >>>\Eagle Dynamics\DCS A-10C\Config\View

 

So I could recreate your environment and your views at my system. - and have a look what causes this and how to fix.

 

Please put all requested files in a single zip. Make insider this zip four different folders containing exactly the files I asked for.

Name this folders A,B,C,D - so I know exactly what I'm looking at.

Feel free to put in each folder a TXT for further explanations.

 

And I need your used aspect-ratio of your "camera"-viewport to be able to make sure that I will exactly see what you did.

Edited February 23, 2012 by PeterP

[Nate--IRL--]

OK so, removing all the *view*.lua files does indeed restore my desired modified snapviews.

 

HOWEVER, I can find no way to stop my controls from being remapped ... even if I delete every single file other than 'mission', still my controls are messed up. In a simple takeoff mission that I created long ago, my controls work fine. But as soon as I load another mission, suddenly roll and pitch are reversed and get 'stuck' in either full forward/backward/left/right after I move the stick.

 

Is this not a common problem? You guys can just take other people's missions and jump right in?

 

Please attach a mission that you experience this with. Have you any axis mapped incorrectly in the game mode control options perhaps? It could be that mission is set to use GAME mode. Try Clicking "Use these options for all missions" in the options menu.

 

Nate

[GregP]

Thanks for the responses, guys. I'll pass on the missions that are messing things up tonight when I get home.

 

With more testing I realized that not ALL missions get messed-up controls ... it seems that most ED missions (for example In The Weeds, Defend Camp Yankee, and Sitting Ducks, and the campaign missions) work just fine, but user-made missions such as =STP= Dragon's Mission and Training Packs and StrongHarm's "Build-up In Patara Valley" always mess up my controls. It seems that Smerch Hunt also messed them up, even though I believe that is an ED mission file.

 

Anyway, thanks for the help so far, guys.

[GregP]

Honestly, I'm not sure what snapviews are (sadly that's true, though I have seen/heard them discussed frequently on the forums and over Teamspeak). You can press some kind of button and have your view snap to a location?

 

Snapviews are views that you can define such that when subsequently pressing the corresponding button will take you directly to that view again. As such, they're perfect for getting zoomed-in views of MFCDs, instruments, etc. There are two ways to access them:

 

1) Momentary snapviews: Press LWin + KPx, where x is 0-9. This view is only active for as long as you hold down the button combo.

 

2) Sticky snapviews: First press and release RCtrl + KP0, then press and release KPx, where x is 0-9. This will 'toggle' the snapview such that it will remain fixed in that view until you press RCtrl + KP0 again.

 

So how do you define the snapviews? I believe some are defined by default, but they may or may not be proper for you based on the resolution you use. For my setup, for example, none of the default snapviews are adequate, because I run a 6400x2160 resolution across 4 monitors, which is most definitely not what the devs had in mind when setting them. :)

 

To set your snapviews:

 

1) Change ‘UseDefaultSnapViews’ to ‘false’ in View.lua

2) Change ‘DisableSnapViewSaving’ to ‘false’ in View.lua

3) Move the viewpoint to your desired location (refer to the Key Commands PDF for the key combos to pan, tilt, zoom, etc.)

4) Press LWin + KPx, where x is 0-9

5) Press RAlt + KP0

 

And you're done.

 

Even though I use TrackIR to pan around and zoom in on the cockpit, I still find snapviews to be tremendously useful. I have mine set to:

 

KP1: Radios

KP2: NMSP

KP3: CDU

KP4: left console

KP5: HUD

KP6: right console

KP7: left MFCD

KP9: right MFCD

[CarneyUK]

Just a quick question? Do you have in your Options menu within the sim....

 

[] use these settings for all missions, checked?

 

Also would this stop missions being able to change your settings. Complete novice when it comes to all these .lua files but just adding some simple thoughts.

 

Hope you get it sorted!

[GregP]

Just a quick question? Do you have in your Options menu within the sim....

 

[] use these settings for all missions, checked?

 

Also would this stop missions being able to change your settings. Complete novice when it comes to all these .lua files but just adding some simple thoughts.

 

Right, that's going to be the first thing I check when I get home today. :) Also I should note that these missions don't actually change my settings -- if I go into the controller options in-game they're all correct -- they just somehow get overridden during the mission.

[CarneyUK]

Well I hope it works...but don't get your hopes up.

 

There is also some sort of 'Prepare Mission' setting in the GUI manual. Never used it myself, but it can be used for the stuff below, it could possibly be that someone in the mission design has used this and that has saved some settings? Again a stab in the dark but worth a look:

 

PREPARE MISSION

 

The PREPARE MISSION mode is used for integrating navigation and environment data into the saved mission file. When near the end of creating a mission, you can start the mission in the PREPARE MISSION mode (it will look much like usual FLY MISSION start) and configure various avionics in the cockpit. Your avionics settings can then be saved and will start in the saved states whenever other players open the mission. The following avionics settings can be saved for the A-10C using the PREPARE MISSION function:

 CDU. All adjustments except the flight plan from mission editor.

 IFFCC. TEST menu settings.

 MFCD. Lower line OSB assignments.

 SADL. User ID and other NET adjustments.

 TAD. TAD profiles.

 TGP. Laser code, integration, calibration method, gain settings, TAAF altitude.

 DSMS. Mission Control Page data, weapon profiles.

 Radio manual and preset frequencies.

 

Once your avionics are setup as desired for the mission, exit the mission and press the SAVE button in the ME once again to save all of the prepared data in the mission file.

 

Everything is worth a try!

[Shootist]

Come to think of it, I have not seen this behaviour with myself in a while now, Dragon's, Strongharm's or otherwise, and in that while I have done a complete reinstall with 1111. Checked my options just now and that "use these settings" box is checked. So, it may indeed be just that.

[GregP]

Update:

 

1) I verified that I do in fact have "use these options for all missions" already checked.

 

2) I deleted all controller axis bindings in game mode, and still I have the weird control behavior.

 

So that's those two possibilities ruled out.

 

I've attached two versions of the Smerch Hunt mission: the default version and a version with all LUA files removed ... both mess up my controls. As a point of comparison, I've also attached the default In The Weeds missions, which works just fine, with or without the LUA files that are included in it by default.

Missions.zip