Bog9y

Is anybody else having more crashes since installing the mod? DCS crashes whenever I try load a 2nd mission in mission editor(first mission loads and plays fine). Trying to figure out if it's the mod or something else?

Yeh,close up the water looks good. But when you fly above it , even as low as 500 ft, it is too dark and featureless. Especially if it's in the shade of a cloud.

A few months later now, any updates on VR performances with 2.7 with the 6900XT vs 3090?

When I use the NVGs in the AV8B the green circle (nvg vision) appears quite small, as if the nvgs are too far away from your eyes. It's great that I can see around the NVG circle but I would like it to be a bit bigger. Is there a way to do this?

That fixed it!! Thank you. But I dont get the lights at night time, not sure why.

Wow! Thanks for such a quick and detailed reply! I was sad to think I was not able to use the static template. I will try the fix, don't care about the integrity check. Thanks!

Is anybody else having issues with the static template for Kobuleti? I can load the template in mission editor but if I click on an object or load the mission to fly it I get an error and DCS crashes. This is the error message :

I read that the mod has been updated already to work with 2.7

What do you lose by doing this? I can think of the following: - kneeboard pages - mods - saved missions (?) Do you keep your control option keybinds? Is there anything else to consider before doing this?

Using a Reverb G1 VR headset, terrain object shadows to default. So with 2.7 I noticed that the shadows of objects (like trees) seem to appear/disappear in a line as you fly over them. It's hard to explain exactly what I am seeing but as you fly along it's very noticeable that object shadows seem to disappear as they pass below the aircraft/a Field of view. It's as if the shadows disappear when the object is about 0.1 nm from the aircraft and creates this weird effect as if something is moving in the corner of your eye. Did anybody else notice this? Is there a setting I should change to fix this?

Ehm...not sure, never tried. I don't remember seeing the mouse under the USB devices in RS Mapper.

Is it reasonable to believe that the performance boost some people are seeing in VR is because of the lower quality clouds? So it stands to reason that if they fix the low quality and improve it we can expect VR performance to go down the drain? Personally I can't really tell if my performance is better...it kind of feels the same as 2.5.6 without a shaders mod. 2080S card , 5900X & Reverb G1. The water does seem too dark though, as do the shaded areas under the clouds. Turning the gamma up makes everything too bright when you are in the sunny areas.

Glad it worked for ya! I love how easy RS Mapper is to use, I use it for a lot of my switches for my AV8B pit. It's just easier than changing the LUAs.

For example, for the Flap switch. Pos 1 is Cruise flaps, middle is cruise, pos 2 (down) is STOL. So in DCS control options, I assign the pos 1 to pos 1 on the switch. Pos 2 to position 2 on the switch. The middle position i assign a keyboard command, let's say it the key "F". In RS mapper I can assign the keyboard command "F" when button 1 & 2 are released.

RS Mapper is your answer for a 3 way switch. you assign a keyboard command for the center position in DCS then assign that command to the center position in RS Mapper.

Awesome! Thank you so much!

Quick question about the fuel ladder. Where does the 1200 lbs per 15 mins come from? I understand it's based on max endurance speed but at what altitude and what drag index? Is it based on a basic drag index or actual load out?

Great documents! I've been searching for an explanation of the fuel ladder and it's impossible to find on google! Thank you!

No, I haven't. That one and the bingo knob are my nemesis(es/ie?). I have asked Razbam for the title of the bingo knob coding but they havent had time to look that up yet. I believe the altimeter knob is the same type of coding as the bingo knob , a "default axis cycle ". And as I understand it you have to code those as "Icommand-title-incr/decr". But without knowing the title you wont be able to code it. I could be wrong though.

Yes, they did issue a "combat aircraft fundementals" manual in 2016, not seen an updated version since. It's missing a few bits and as far as I could tell didn't have a clear layout of the training sorties planned for a B course. The other option is just following the IQT campaign that's available. My problem is that I love seeing the real stuff and creating my own missions based on that.

Thanks, I'll have a look at the RWR volume. I have made it an axis command (listed above) and I'll check the volume issue.

Thanks, I have been told these bindings will be implemented with the next update after 2.7.

One thing I forgot to mention is that I also amended the coding in the COMMS section for the RCS panel. The original LUA has the OP MODE of the RCS coding miss-spelled with the word MODE as MOD. The numbers for the positions are also incorrect. It's coded with some arbitrary intervals but it should be 20 degree intervals to assign rotary switches. So these 6 lines should be replaced: {down = radio_commands.Switch_OP_MOD, cockpit_device_id = devices.RSC, value_down = 0.05, name = _('UHF RCU-8150 Operational Mode: OFF'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MOD, cockpit_device_id = devices.RSC, value_down = 0.15, name = _('UHF RCU-8150 Operational Mode: TEST'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MOD, cockpit_device_id = devices.RSC, value_down = 0.35, name = _('UHF RCU-8150 Operational Mode: TR+G'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MOD, cockpit_device_id = devices.RSC, value_down = 0.45, name = _('UHF RCU-8150 Operational Mode: TR'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MOD, cockpit_device_id = devices.RSC, value_down = 0.55, name = _('UHF RCU-8150 Operational Mode: ADF'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MOD, cockpit_device_id = devices.RSC, value_down = 0.65, name = _('UHF RCU-8150 Operational Mode: CHNG PRST'), category = _('Radios Control')}, REPLACE WITH THIS: {down = radio_commands.Switch_OP_MODE, cockpit_device_id = devices.RSC, value_down = 0.00, name = _('UHF RCU-8150 Operational Mode: OFF'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MODE, cockpit_device_id = devices.RSC, value_down = 0.20, name = _('UHF RCU-8150 Operational Mode: TEST'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MODE, cockpit_device_id = devices.RSC, value_down = 0.40, name = _('UHF RCU-8150 Operational Mode: TR+G'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MODE, cockpit_device_id = devices.RSC, value_down = 0.60, name = _('UHF RCU-8150 Operational Mode: TR'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MODE, cockpit_device_id = devices.RSC, value_down = 0.80, name = _('UHF RCU-8150 Operational Mode: ADF'), category = _('Radios Control')}, {down = radio_commands.Switch_OP_MODE, cockpit_device_id = devices.RSC, value_down = 1.00, name = _('UHF RCU-8150 Operational Mode: CHNG PRST'), category = _('Radios Control')},

If it's the normal COMM 1 & 2 volume controls try adding these 2 lines to the joystick default.lua file in the AXIS section (right at the bottom): {action = ufc_commands.Knob_Comm1_Vol, cockpit_device_id = devices.UFCCONTROL, name = _('COMM1 VOL')}, {action = ufc_commands.Knob_Comm2_Vol, cockpit_device_id = devices.UFCCONTROL, name = _('COMM2 VOL')},

Do you mean the normal COMMS 1 & 2 volume controls on the UFC or the comms volume on the RCS?