TAIPAN_

Interesting, I never knew them by their keyboard binds as I use my mic switch always. Funny that mine DOES have "Ralt + \" in the keyboard binds list, maybe because I bought the F1 quite late and didn't get the original binds in my folder. I do have the double "T" bound though, and deleted the bind from the Search light but it doesn't help. I guess the PTT just isn't implemented and they force easy comms or are using the comms menu for radio. I don't actually know how easy comms work so can't say for sure. The way we have to select the radio push button first though makes me think its converted the comms menu into its own hardcoded push to talk and not actually using easy comms. In any case, I'll survive on that button until it changes...

Thanks yep, all those expectations are fairly normal and radios are selected. It just doesn't work in the F1 contrary to every other module. Found a post on reddit that says PTT bind doesn't work in the F1, I guess we wait and see. But will check in later if you manage to bring it up somehow. The info about MKR+TP being intercom "Marqueur + Téléphone de Piste" is from Chuck's research for his guide, it's still in draft so he may have it incorrect and I don't know french but he does so I kind of trust him unless I hear otherwise.

That's correct, Ralt + \ (or whatever PTT button on the joystick is bound). The catch is that the correct keystroke doesn't work At least not for me

Yeah it doesn't make a difference. With full fidelity aircraft usually you can still bring up the radio menu with the PTT and make a request of ground crew, but what happens if the intercom is OFF or canopy is closed is just that they ignore you... but the menu is still there. In this case the menu doesn't even appear on PTT. FYI the MKR + TP is "Marqueur + Téléphone de Piste, Marker + Ground Communications". It also has a depress select function. Will probably be useful on the ground with canopy closed once the PTT changes. However I totally overlooked something - the PTT and alternative PTT don't work in the air either. They just don't work at all ever. You can communicate with the comms menu binding backslash\ that directs you to whichever radio is selected by the radio selection pushbuttons (or the intercom). I tested both keys and buttons. SRS works fine, but that's a different binding in the SRS program. Just the two PTT bindings to talk to AI don't work. Maybe I've setup my radios wrong or something, I've attached a screenshot where I have the green radio selected before trying the bindings in the other screenshot. nullnull

Awesome thanks! I tried to add some of them as Axis, but unfortunately only the MISS volume works as axis, the others tend to get a bit out of sync (so do the 3 Sight Brightness controls if you add as axis). Interesting that we can't use the PTT control at all to talk to ground crew until after we've selected radios, I'll be using the second direction on my mic switch to map the comms menu until I get started up I guess.

Does the Mirage F1 cockpit have volume controls for: 1. Missile Tone (eg AIM9, Magic) 2. Radar Detector or RWR sounds 3. TACAN volume I haven't been able to find any, are they yet to be implemented or was the real F1 like this? Thanks

Thanks for this mod. After some testing I decided to keep Line 87 & 88 on as default. Commenting it also removes effects like the Canopy Scratches that make you feel like you're canopy is really down and over you (tested in the F14 mostly). However I did keep the line 101 change which reduced the extremity of some effects, but I adjusted it to 0.4 instead of 0.2 (default is 1.0). If find this looks quite nice in the F14 Tomcat and the AV8B Harrier. There's still an effect, but it just looks natural now. All personal preference

Yes very much needed. This pure scripts integrity check is becoming a real problem for us multi monitor users that need to move the control indicator, kneeboard, and helicopter AI gunner indicator because the default code puts them off the screen. Even Enigmas and Hoggit have turned on pure scripts

Screenshots already include your exported MFDs, in fact you can't take a screenshot without them unless you crop them off.

Yes, it will add waypoints after the last waypoint. 2 people will need two separate installs of theway

Thanks for the update on the F-14 engine panel! Looks very nice so far, haven't had time to fly much yet just ran a quick test. Also looking forward to the A10C and AV8B changes

Thanks - this solved my issue with the dark Winwing MFD screens! I had to make two different presets, one for "green" MFDs and one for black & white like the A10C. The B&W type MFDs need alot less changed.

I'm still on the old version of the mod (for 2.7.11) and don't have this issue. I haven't tried the new version yet though. Might be one of the changes since then?

I think he may mean 6 miles where the mod has the dot opaque? After 6 miles it gets exponentially more transparent - this makes viewing it really dependent on the background. Against the ground textures and trees maybe not, against pure blue sky or pure white cloud maybe yes. By 18 miles it is completely transparent. I'd be curious where ED got their distance info from when originally designing it on older graphics/monitors 20 years ago (1080p or 800p etc). Maybe there was some source, though it does feel that something in between would be better.

It's funny in DCS though because many certainly do prefer the MAIN position, due to many MP servers setting the default fuel loadout with wing tanks empty because of the long endurance of the A10. Also due to the typically short flight distances we fly online, compared to real life. Great kneeboards though thanks, and I often do use the WING position because I prefer to take my time and have plenty left for contingencies.

Oh wow looks like I found the wrong Oceanic server. Smiladon had linked one on an IL2 post a few years ago but it looks empty. Just joined this one thanks, will have a chat later cheers

This is true, leave the mod/fix available with IC until ED provide their fix. The mod clearly fixes something - I'm sick of seeing youtube videos showing you how to lower your resolution below 1080p and stretch it to your whole full screen just to allow spotting. If the devs can test on ultrawide/4k and compare to 800p it would allow a better outcome. Ideally there should be no difference in ability to detect if the scaling is done right.

Please don't include labels in the same sweep of adding to the IC. There are great mods out there that tweak the neutral dot to make it fade realistically, and these will only work on servers that enable labels anyway (server owners can disable labels already and it won't even use the label files) Only dots.fx needs to be worked on

Ahh ok yep, that was the other thread. I started this new thread about the DDIs failing. However I haven't been able to reproduce it since. Probably ok to close and if it happens again I can create a track etc.

Hi Wolfpac, long time no see. Glad to see you're still going strong with sims and mods. I had to give up simming for personal reasons back in the OW days (10 years ago??) but have been able to come back since COVID time. I left a message in the OW discord. Might have an idea how you can solve the IC thing, though you may have already tried it since you mentioned saved game cockpits. It involves generating description.lua with modelviewer and making it a selectable cockpit livery, not sure if you did all the steps. Message me here or Discord DanW#8271 Would be great to catch up

Not saying you don't know what you're talking about, or that you didn't title a topic.. just not THIS topic. The title of this topic was by IceyJones, it's probably just a case of responding to the wrong thread? null

I don't understand what is correct, you're saying the Walleye having intermittent failure to Uncage on the DDI is correct? So only some Walleyes can target things and others are duds? EDIT: In any case I'm unable to reproduce in single player so I can't create a track (this only happened in MP on a longer flight). For now don't worry about it, if it happens again I'll do more work to try and reproduce.

VR isn't the subject, we've gone way off topic it seems.. Me included sorry.

This bug was the opposite to that, there were actual launches but no RWR warning. It's quite common to see a warning without launches, especially if it's launching on someone else. Not saying there isn't an issue, but you'd need to isolate/test it some more and probably raise a separate bug for it.

First part is true (better tracking) Second part is not true (supposed to see virtual cockpit not your own). Plenty of people setup home simulators and turn off the virtual cockpit to show only the view out the canopy. I disagree with "supposed to" just because that's purely personal preference if you like graphics or real objects, which is often decided based on hardware etc.