alexbap

Thanks Hiromachi.

I didn't have much time to test but at least RSBN channel selector nob and landing/taxi lights aren't working with keybindings. They only work with mouse. Direct joystick imput button doesn't work either.

Thanks alot Freddo. Lets hope landing and taxi lights gets fixed soon.

I have two problems with lights. One is that both landing and taxi lights are way to strong (first picture). At night everything become white under their light and even under sun they are overexposing over sun light. It ruins completly the imersion. The second problem is that I have some cockpit lights allways on, even without battery on (second picture) and some underwings lights and inside engine exhaust also on and I can't turn off none of these lights (third and fourth pictures).

On my missions, during ramp start, I configure weapons before ramp start so that I don't need to change switches after. This way I can fly without crashes.

I'm not 100% sure abaut this but this is my understanding of radio item flags. Flags associated to "RADIO ITAM ADD" are just triggered once and if they were previous OFF. Once a flag is activated by a radio item it doesn't get triggered again by repetitive use of that same radio item because it was already ON. What you can do is to create a second trigger after every "RADIO ITEM ADD" trigger that will turn off the flag associated the radio item, a couple of seconds after this was turned ON. This was that flag is indeed get triggered with repetitive use of radio item. Hope this is understandable.

Thank you for your help, Rudel. I finally figure it out and as 99% of the cases the problem was between the joystick and the chair.:doh: When I made the mission I was counting on flag associated with first radio item to trigger the second radio item with a couple of seconds delay and in mission context this made sense. The problem was that during testing I was not using first radio item and therefore not triggering the flag that would allow second radio item to apear. A tipical case of sleep privation provocking lack of awareness. I spent more than an hour trying do solve without sucess. Today, in 20 seconds I figure it out. Again many thanks for your help.:thumbup:

Thanks Rudel, thats what I thought, but my radio items aren't showing in mission when use more than one trigger. Can someone please verify if this isn't bugged? Thanks again.

In my mission I want to add radios items over the mission time as long as some events occur. So I've created triggers with "RADIO ITEM ADD" as needed. The problem is that after first "RADIO ITEM ADD" trigger that was created at "MISSION START", no more radio items are created. The only way I found to create more than one radio item is to put all of them on just one trigger but I don't want this. Is this as intended? I thought we could create diferent radio items on diferent triggers. And one more question regarding "REMOVE RADIO ITEM". On "name" tab do we have to write the entire message of radio item we want to delete so the game can identifie it? Thanks.

I have a GTX1060 (6GB) and on Persian map and I don't have frames drop using radar. Tested low altitude over city. Today, if I remember, I'll try on Caucasus over trees. I'll also post my graphic settings so you can compare. Could this be because of radar reading trees? They are very heavy on system just for displaying them. Imagine calculating radar bouncing.

I really don't know. I already use other mods that don't pass because I only fly coops and everybody that I fly with have the same mods so I can't tell if this mod is conflicting or not. But in any case is simple to try. If anyone can confirm its integrity check would be nice.

Hi all, I edited R_NAV_data_PersianGulf.lua file so that we have almost all default Persian map VOR stations in Mig-21 RSBN channels. I just left out a few from outer regions of map, outside populated areas. Theres also 1 arc station (1-I,7) over Jiroft airport. RSBN channels from 1 to 18 are the same as default and I added channels 19 to 32. There's also 2 kneeboard pages with stations location. To install copy R_NAV_data_PersianGulf.lua (overwrite) to C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MIG-21bis\Cockpit\Systems\ and RSBN_Persian1.png and RSBN_Persian2.png images to: C:\Users\********\Saved Games\DCS\Kneeboard\MiG-21bis\ Notes: -R_NAV_data_PersianGulf.lua is overwriten with every patch so you have to copy it again. -Morse codes were copy/paste from existing ones for now. I plan to define new ones over this week. -If someone form Magnitude 3 LCC wants to use this file, please feel free to. It would be nice not to have to copy it with every update. https://www.digitalcombatsimulator.com/en/files/3309257/

Both of these problems are bugs, already reported, so no. Your start procedure isn't the cause of CTD or ASP malfuction.

Since last past I also have constant DCS freeze with Mig but I can't relate to any specific weapons configuration. I've been flying only on Persian Gulf so I don't know if this hapens on other maps.

I don't want to pick sides on this discution because I think that current FM need a lot of love but here is a video af a real Mig21 puling a sustained turn at 30 AOA at 2:20 and a high resolution photo of that plane cockpit so you can check numbers on instrument. And this was on RIAT 2019 so there's safety margin on that. Lets face it. The vast majority of us are just entusiast without real and suported knowledge of this.

I was about to post this exact problem. I can confirm that.

I just did a small filght but to me it feels the same. The only diference I noticed was trim light goes off with much less trim and that smooths the rotation. I was already taking off with out any trim so to me it is the same.

Am I missing something? Did we get new clouds with last update?

Same here. Skin is still not updated, but thanks anyway Apache. Probably a minor mistake easily fixed soon.

Thanks alot Apache!

As tittle, can we have the campaign skin updated? Right now, it has a USAF reflection under it that simple ruins the imersion. Thanks.

From Chuck's F-86 guide, page 43: "Note The nose wheel steering system will not engage if the nose wheel is more than 21 to either side of center. Should the nose wheel be turned more than this, it must be brought into the steering range by use of the wheel brakes When the nose wheel steering activation button on the control stick is released, the nosewheel steering system starts to work as a shimmy damper and the nose wheel goes to the self castering mode."

Its already reported. Weapon release is broken after this update. Lets hope a small fix comes next week.

Amazing work.

CMDS_ALE47.lua inside: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device\ just remember that on some weekly updates it resets to default.