skybaby68

https://www.digitalcombatsimulator.com/en/files/3347594/ I wanted to bring something slightly new to the Training table, to both help the novice F-4U pilot as well as to aid as a handy refresher. So here it is. A fully illustrated Training mission from beginning to finish, hundreds of interactive plates covering Shore Start Up, Take Off, Shore Landing & Shutdown, Carrier Take Off, Carrier Landing & Shutdown, Readying Weapons & How to use the YEZB Navigation Radio. It also has a basic Airfield Ground Attack mission, with & without an Wingman. It can be flown solo or in Co Op. It's ideal for VR users. The Plates will appear onscreen & disappear when the particular step has been completed etc. It's a great way to learn the ways around the aircraft in real time. Also features custom ai voiceovers & a period Naval Air Squadron music score in places. I've left the mission unlocked so the user can 'tinker' to their likings if needed. The player skins depicting 738 NAS were created by 'keefyboy'.

Ah how very interesting. Thank you for posting these Fenrir.

Title says it all really. All generic RAF squadron codes have 'always' been wrong in DCS WW2 aircraft. Port-side only. It would've taken about 25 seconds research to see that historical RAF codes always had the 2-letter squadron code 'before' the roundel. followed by the individual aircraft letter 'after' the roundel. This is a huge oversight and I'm sure, one that would've easily been fixed but never has. Is there hope that this can indeed be fixed?

Hi Max. Many thanks for your response. They're all my missions from the editor & no views are locked out. the 'enforce' tick is in place on Externasl Views & F10 Map All in the Mission Editor options. It's also across the board, in all forms of DCS missions or Campaigns for me. I've not changed any settings whatsoever since the update so I'm going to put it down to a very strange anomoly on my part & try backing up/deleting the config folder etc. Good at least to know it's not a problem that's affecting all.

Tried on F-4U, Spitfire & P-47D in Marianas WW2 map, Caucasus & Normandy 2.0. I have 3 PC's & 3 accounts (LAN etc) & same results on all PC's since update. No F7 views, no F9, no recycling through other a/c using F2. This is so strange indeed.

Anyone else having 'F' view problems since this update? This is so strange & has only occurred since the update. F1, F2, F3, F4 & F5 keys all work as per normal on player aircraft but F2 no longer cycles other aircraft. F7 no longer jumps to ground units & F9 no longer cycles shipping. Ctrl + F11 seems to work as normal (as free camera). I've tried it on different keyboards, no mods active, different aircraft, different maps & have even checked the keybindings (which are fine btw, F7 registers as F7 ground units view when pressed, and so on). Never experienced this problem ever before and all was fine before this patch. What on earth is going on? I've put a post in the views section of bugs but it's not getting much coverage there.

Since downloading the latest update (October 2025), my 'F' keys are suddenly no longer working. They seem ok for 'player aircraft' ... but that's about it. F7 no longer works to cycle ground units, F9 is dead (no longer cycles shipping), F2 will show external view of player aircraft only & further presses of F2 no longer cycles other aircraft. I've checked the key bindings & nothing has changed there, just ingame. My keyboard hasn't changed, no peripheral changes & have disabled all mods as per usual with new updates. Tried different modes (mission editor, mission, quick mission, different keyboards also).

"Aircraft are loud?" Not the most helpful tip ever as this is clearly an oversight. AI Corsairs have absolutely no spatial sound like all other vehicles & aircraft in DCS. No matter how far away the aircraft is, within a distance of around 1/2 to 3/4 mile, they will sound as if they're right next to you until they're outside that 1/2 mile bracket then they're silent. It's very distracting tbh.

Checked other created missions on the Normandy 2.0 map & same thing. All other AI units like B-17G, C-47, Spit, P-51, P-47 etc are fine but every A-20G is minute in scale. Ah great thankyou. Good to see it's been reported already.

This is a weird one. Since the DCS 2.9.20.15010 update, my A.I. A-20G aircraft are miniscule in scale. The pic shows the A-20G IN THE FOREGROUND with the crew standing 'behind' it after engine shut down. So far, only tried with the A-20G on the Marinas WW2 map at Orote airfield on Guam. I was working on this mission of mine last weekend & all was fine so has to be the latest patch as the culprit.

Nope. Bypass the MiG. Bring on the Work horse

Tried that ... nothing. Nothing under 'access', 'maintenance', 'panel', 'door', 'ammo', 'gun'. But then I came across it in 'Systems' .... Service Hatches Open/Close ... Right Alt + Right Shift + H Problem solved lol.

What about the gun ammo panel doors on the nose that is shown in 4 out of the 6 product pics on the 'Details' section of the F-5E Remasterd? I can't find any bindings or find any way of opening those outer panels? Would be a very strange and slightly mis leading selling feature if you couldn't access them when the product pics rely so heavily toward them.

Get a grip. It's just a game with hundreds, maybe thousands of dollars worth of invested modules, tens of thousands of pounds worth of sim equipment. It's just a game that stops you from utilising all of that with a simple Login discrepency. If it is 'just a game' scenario with you, why bother to become involved in this thread with such a child-like passive aggressive comment?!

2 PC's for me but I have 2 seperate accounts & each PC is only ever logged in to its individual account so there is never any crossover etc & besides, this problem has only become really bad in the last few weeks whereas I've had a problem-free time of it with multiple accounts for years.

Me too. It's so frustrating. Especially when mission building. It's now a common occurrance and has been for around 3 weeks to a month now.

Yep same here. The noise is insane after a few mins. The best WW2 bird of DCS currently unflyable. Tried disabling all mods, tried at cold start, hot start, no difference & seemingly no way to rid of it.

Yes I'm using the CLTD 1.40 version of mist as well as using a UH-1H. Infact the only difference between what I was trying to get to work and your example was the unit name (I had helicargo1, same as pilot name), and the fact that you added what looks to be an additional small script for a fob but fair play... yours works and mine doesn't so it's clearly user error on my part. Thanks so ,much for providing me your working example, I really do appreciate it & yes I couldn't make any sense of the demo mission whatsoever & besides even that didn't work for me (no CTLD menu on F1). Many thanks to you

I guess I'm a bit late to the party? I wanted to try this CTLD and have followed all the youtube videos precisely, downloading & installing the mist & v1.40 of the ctld in the 'do script file' ... name my helo helicargo1, a trigger zone as pickzone1, 3 m4 troops for pickup as extract1 etc etc. Insim thjough, whatever I try ... the F10 menu gives me F1 as List Radio Beacons, with F2 & F3 being JTAC & RECON. Is there an easy workaround as I don't have Discord & have been trying for hours to get this to work. Any help would be very much apprecaited

I should also add that the connectivity is fine, no warning signs under USB ports in device manager, power saving boxes unticked, correct setup as per instructions and using USB2.0 instead of USB3.0. Power not an issue as I've a 1000W PSU. The Crystal battery 'always' remains fully charged.

This is good to hear because it's getting worse. You can depend on Eyetracking disengaging around 3 or 4 times per every 30 mins in DCS. Also there is no easy or sure-fire way to turn the headset on and off. As soon as I turn PC on, the PiPlay software asks to connect which I allow it to, then sometimes I have to manually turn the geadset on by holding the power button down for 4-5 secs and 'eventually' it 'may' connect; other times it just will not connect, causing a PC restart (I regularly check device manager to ensure a tick hasn't been put into the power saving box). And shutting down ... it just will not stay shut down no matter what I try ... to select 'shut down' on piplay before sutting down, physically powering down, it will just come back on after a few seconds. For £1500 (plus the plethora of extra accessories you 'have' to buy to gain a relatively non-painful experience), it's a complete mess of a headset ... it's becoming unenjoyable now with so so many shortcomings.

March 2024 - Still happening. Spent hours creating a detailed map at Nevatim and on testing I couldn't work out where the mass firebomb was coming from until I noted 3 AI aircraft air spawning over the runway and not from their allocated park slots of 01, 03 & 05. When you say Priority Highest. Do you mean ... within the 1st couple of years?

Also I've disabled all mods from JSGME, deleted contents of metashaders & fxo folders etc & ran the repair. No difference.

Hi Flappie. Yes I've done that and keep periodically checking that it's still an exception.

I have 3 home PC's, 2 running DCS in VR and 1 running in 2D PC 1 & 2 are indentical: 19 14900K with 4090, 64GB DDR5 RAM, but PC 1 is running Pimax Crystal & PC 2 is running Quest 3 Both are running OpenXR and since 2.9.3.51704, both of the above PC's will, at around 60% of the time, cause the entire PC to run at a snails pace when DCS finally gets to the main menu. I have the OpenXR FPS counter running and it plummets from the usual 91.0 down to 2, sometimes rising to 30 or so then back to 1-2. Most of the time it takes the PC with it, having to exit DCS via task manager & hope the PC gains enough momentary speed to be able to exit DCS and try again. Invariably it will also do it coming out of a mission, back to the main menu. My 3rd PC running DCS in 2D is an i7 11700K with a 3080Ti & 64GB DDR 4 and is unaffected. It's worth noting that this is an all new problem since the last update. All PC's were running fine beforehand. If anyone can relate to these problems and can guide me out of this hole I'd be most grateful. dcs.log-20240305-185237.zip dcs.log-20240305-145615.zip dcs.log-20240304-210515.zip dcs.log-20240303-004138.zip dcs.log-20240225-152737.zip dcs.log-20240227-042437.zip dcs.log dcs.log.old