MiG21 - 1.2.12 Open Beta

[monsterman]

I've get the problem no gauges fonctionnals, after selected the option custom cockpit it's was OK ! this is my Options.lua file !

 

options = {

["difficulty"] = {

["birds"] = 660,

["cockpitLanguage"] = "english",

["cockpitVisualRM"] = true,

["easyCommunication"] = true,

["easyFlight"] = false,

["easyRadar"] = false,

["externalViews"] = true,

["fuel"] = false,

["geffect"] = "realistic",

["iconsTheme"] = "nato",

["immortal"] = true,

["labels"] = true,

["map"] = true,

["miniHUD"] = false,

["optionsView"] = "optview_allies",

["padlock"] = false,

["permitCrash"] = false,

["radio"] = true,

["reports"] = false,

["setGlobal"] = true,

["tips"] = true,

["units"] = "metric",

["userSnapView"] = true,

["weapons"] = false,

},

["graphics"] = {

["HDR"] = 0,

["MSAA"] = 3,

["OculusRift"] = false,

["TranspSSAA"] = true,

["aspect"] = 1.6,

["civTraffic"] = "",

["clutterMaxDistance"] = 500,

["cockpitShadows"] = true,

["color"] = "32",

["disableAero"] = true,

["effects"] = 3,

["fullScreen"] = true,

["haze"] = 1,

["heatBlr"] = 1,

["height"] = 1050,

["lights"] = 2,

["multiMonitorSetup"] = "1camera",

["preloadRadius"] = 56798,

["scenes"] = "medium",

["shadowTree"] = false,

["shadows"] = 1,

["sync"] = true,

["textures"] = 1,

["treesVisibility"] = 6552,

["visibRange"] = "High",

["water"] = 0,

["width"] = 1680,

},

["miscellaneous"] = {

["Coordinate_Display"] = "Lat Long",

["accidental_failures"] = false,

["f10_awacs"] = true,

["f11_free_camera"] = true,

["f5_nearest_ac"] = true,

["force_feedback_enabled"] = false,

["headmove"] = true,

["synchronize_controls"] = false,

},

["plugins"] = {

["F-86F"] = {

["landSeatAdjustF86"] = true,

},

["FW-190D9"] = {

["assistance"] = 0,

["autoRudder"] = false,

},

["Ka-50"] = {

["altTrimmingMethod"] = false,

},

["Mi-8MTV2"] = {

["Mi8RudderTrimmer"] = false,

["altMi8TrimmingMethod"] = false,

["controlHelperMi8"] = false,

["weapTooltipsMi8"] = false,

},

["MiG-21Bis"] = {

["CustomCockpit"] = true,

},

["P-51D"] = {

["assistance"] = 0,

["autoRudder"] = false,

},

["TF-51D"] = {

["assistance"] = 0,

},

["UH-1H"] = {

["UHRudderTrimmer"] = false,

["UHTrackIRAiming"] = false,

["altUHTrimmingMethod"] = false,

["autoPilot"] = true,

["weapTooltips"] = false,

},

},

["sound"] = {

["GBreathEffect"] = true,

["cockpit"] = 0,

["gui"] = 0,

["headphones"] = 0,

["music"] = -100,

["radioSpeech"] = true,

["subtitles"] = true,

["volume"] = 0,

["world"] = 0,

},

["views"] = {

["cockpit"] = {

["avionics"] = 4,

["mirrors"] = true,

["reflections"] = false,

["russianHud"] = false,

},

},

}

[Esac_mirmidon]

Same here.

 

After selected the option custom cockpit all things comes alive again. It´s a very strange issue. Also i can´t find where are the cockpit options for different colours/languages.

[dmayan]

Same here.

 

After selected the option custom cockpit all things comes alive again. It´s a very strange issue. Also i can´t find where are the cockpit options for different colours/languages.

 

Yeah. Ticking that box made my cockpit functional again.

[uboats]

Same here.

 

After selected the option custom cockpit all things comes alive again. It´s a very strange issue. Also i can´t find where are the cockpit options for different colours/languages.

 

Yeah. Ticking that box made my cockpit functional again.

 

 

The script didn't implement the list but just checkbox, so Novak wants you to choose one mod and put it to the custom folder. In this case, we have only one choice, and the cpt tooltip language is still bound to the cpt texture.

 

Here is my updated script which implements drop-down list. In this one, it can recognize any number of customized cpt texture folders and the cpt tooltip language is unbound from texture (e.g. you can choose ru cpt while using english as cpt tooltip language)

http://forums.eagle.ru/showpost.php?p=2227233&postcount=1

 

could anyone paste the content of mainpanel_init.lua under MiG-21Bis/Cockpit/?

Edited December 3, 2014 by uboats

[Esac_mirmidon]

This .lua file is very long to post it here.

[uboats]

This .lua file is very long to post it here.

 

just the indent part for

dofile(...Config/options.lua)
xxx = xxx[options][mig-21bis][customizecpt]
if xxx then

else

end

 

thanks

[Esac_mirmidon]

I can´t find this part in this file.

 

Line number?

[uboats]

I can´t find this part in this file.

 

 

 

Line number?

 

 

I'm not sure, or could you copy the first 100 lines and send it to me via message? thx

[Esac_mirmidon]

I can post here the file, no problem.

 

link

[uboats]

I can post here the file, no problem.

 

link

 

thank you.

 

Is this one from formal release 1.2.11 or openbeta 1.2.12? It seems this is not 1.2.12 version.

[Esac_mirmidon]

Nope, it´s 1.2.11

 

If you need the 1.2.12 file i can share it with you.

 

EDIT: XDDDDD

 

The old file is useless for you, XDDDD, you need the new one. XDDDD

 

Sorry.

 

link

[uboats]

Nope, it´s 1.2.11

 

If you need the 1.2.12 file i can share it with you.

 

EDIT: XDDDDD

 

The old file is useless for you, XDDDD, you need the new one. XDDDD

 

Sorry.

 

link

 

Thank you.

just look at the script, there shouldn't be any problem.

When I was working on the drop=down list script, the same thing happen, but i finally solved it.

 

now once your checked it, no issue. What about unchecking the box again?

 

When that problem happen on your DCS, what cockpit it was (en or ru)?

[Esac_mirmidon]

I´m using russian version fo the Mig-21 Bis cockpit.

 

Unchecked= Problem

Checked= Solved.

 

I will try this script when my updating process get finished.

[uboats]

I´m using russian version fo the Mig-21 Bis cockpit.

 

Unchecked= Problem

Checked= Solved.

 

I will try this script when my updating process get finished.

 

so once you checked it then it solved, and if you subsequently unchecked it, the problem came back? If so that's weird, since if unchecked again, there is such variable (now is false) in the options.lua and the script should work fine. While for first time (unchecked), there could be no such variable in options.lua and in my opinion that could be the reason of the issue.

 

I will try it later tonight. If there is no other big changes, my script should work fine (suggestion: before flying, go to option special mig-21bis, in the drop-down list, make a choose (e.g. click default again (no change but do it)) and save). You can also create many folders for Mainstay's cpt mod. But for those, I think you need to modify the description.lua accordingly.

[Esac_mirmidon]

This test was after using your script.

 

Now in the Mig-21 Bis i have only three options ( CUSTOM - ENGLISH - DEFAULT ) but no check box to clic or not.

 

Now with the script all three options works fine, the cockpit is 100% operational.

[uboats]

This test was after using your script.

 

Now in the Mig-21 Bis i have only three options ( CUSTOM - ENGLISH - DEFAULT ) but no check box to clic or not.

 

Now with the script all three options works fine, the cockpit is 100% operational.

 

good to know.

For my script, there is no limit for custom cpt texture, while current one from mig21 limits us to edit custom folder only. You can also try Mainstay's mod using my script, you can use the description.lua in default folder and change the last column of lines from true to false if the dds of that line can be found in local custom folder.

[Esac_mirmidon]

Good to know.

 

Thanks uboat, useful info as always.

[EEch]

Can you please fix problem with mapping thrust on pad buttons? It's not work right now.

Also gears cover just broken when you use nuke payload.

[Justin Case]

Also gears cover just broken when you use nuke payload.

 

No I think they are removed to fit the bomb.

[EEch]

No I think they are removed to fit the bomb.

 

Here two screens, one after spawn second after engine start.

[zaelu]

Can you please fix problem with mapping thrust on pad buttons? It's not work right now.

Also gears cover just broken when you use nuke payload.

 

Yes, this is an ugly old bug.

[Azrayen]

I'm not surprised about the checkbox issue. Indeed, we got a similar case with LotAtc 4 DCS.

 

Explanation:

- the checkbox value should be stored in options.lua

- this file is part of the Saved Games directory, hence it is not updated/modified by the auto-update = just after upgrading to 1.2.12 there is no value stored at all (no true nor false: the line simply doesn't exist in the .lua file)

- the file will be updated (and the value stored) only when the user (you) goes to options>special and check/uncheck the box

- I guess the cockpit for the MiG currently needs to find the stored value, and if not = dead cockpit bug.

 

My suggestions would be for LN to fix the cockpit code so that if no stored value can be found in options.lua, then the code considers the value as false (that's a kind of fail-safe mechanism); and to publish (if not already done) a quick guide on how to use the new options, for the guys that want to try it.

 

Cheers

Az'

[ff4life4]

Anyone noticed better fps. Much better for me now. At my 60 fps limit now :)

[ttaylor0024]

Anyone noticed better fps. Much better for me now. At my 60 fps limit now :)

 

Slightly better on the ground, but after I looked up the cockpit glitch and finally got in the air for the first time in the update, I was promptly destroyed after I drop to 5fps in a dogfight with a MiG-29.

 

In better news, my i5 4690k came in the mail today, so hopefully after tomorrow that won't happen for a long while. The 'ole Phenom II has been struggling pretty hard lately