All Activity

А вот тут поподробней. Не смешно.

ED Team ?

ive got i7 12700kf 64GB ram RTX4070 12GBvram VR Quest 2 At 72hz Msi z690A i cant play vr without the ghosting efect because i can not holdd72 fps Why??? text map is on high, i fly the apache i ve set off core parking in windows ,ohter games are running very fine with no cores are parked , when i play dcs cores are parked, used Process lasso , still can no t hold 72 fps without dlss What the hell is wrong with dcs I think 72fps should hold . i mean in the counter the yellow and the green line are heavely drawing ( like a kid that draws a drawing) Or is just not possible with a rtx4070 to get 72hz in a quest with quest link???

The radar range has been semi recently tweaked in the FC3 module to be very accurate. Expect it to be close.

Welcome to DCS, avoid smoking a Cigar while using Track-IR It's like Flares to fool the Tracker

Well, kind of complicated if having your Hotas and maybe other USB gadgets ( UFC, MFD etc.. ) on one PC and the actual DCS core running on another is what you want. It is first off not ment to be/work/function by design of the involved software and second, even if, it wouldn't make it any simpler or less work even if you knew how. The only thing that may get close to what you may want, lots of guesswork here, is a Client-Server Home setup. That frees up your actual flying rig and puts some load to the server, your old rig. The bigger the mission the bigger the gain as rule of thumb. I would do this anyway, if you have 2 PC's at your hand, it's not uncommon at all. With 10 and 11, you can basically take the drive, or clone it, and PLUG IT IN THE NEW MAINBOARD. It will work and if your Windows was in good shape that is what I would do to avoid reinstalling all the stuff and licenses and configs and settings, weeks, not days of work, at least in my case. The only thing you should do if you take the existing OS install along is uninstall al MB specific software, Audio, BT, WLAN etc. if there are any listed in Apps before you unplug it and before plugging into the new MB. That's all there is. There is no more HAL like XP had that did not allow you to do this. It is on par with Linux, take the drive, plug it in and boot it. Safes alot of installing in many cases. Win will reboot once or twice to sort itself with new Hardware found on first launch, that's normal. If it, against all odds, should go wrong, make a backup of your data FIRST, make two !

The lights above Engine Test Regulator buttons won't light if I press them. I don't know if this is a bug or if this test is not modelled. Thanks a lot.

The files that you install or uninstall are located in DCS <root folder>\Mods\Aircraft. If the module's folder that you just uninstalled, are still there with any content, you can fully delete them without harm to your installation. IIRC, when you command for a module uninstall, those files at DCS <root folder>\Mods\Aircraft are deleted. Do not confuse with necessary files for displaying a unit properly inside "Core Mods" folder. Everyone need those file to be able to fight against and fight alongside with the unit in the simulator environment. Note: <root folder> - Wrote it because that file name is customizable and it goes by default as DCS World, but I'm not fully sure because it is been a long time since I've installed DCS from scratch.

Nice. Glad to have helped.

на пику вышел новый родной стриммер ПикоКоннект 10.6.6,где пофиксили лаги в OpenXR,который там работает без стимВР. https://github.com/owomushi/Pico-Connect/releases теперь не только VD нормально р аботает с игрой

ага,понял.Так и подумал тогда.

Thanks guys for taking the time to write. I know it is only a few GB of data but even a few KB is too much if I don't need it. I am asking how to fully uninstall a module properly that wont break my DCS.

АААА!!! "The Forest" используют маньяки-расчленители для своих тренировок

This is the F/A-18C bugs forum. F-16 bug reporting forum is over here https://forum.dcs.world/forum/333-bugs-and-problems/

Sniper doesn't have "issues"; it's Lightening that has the problem now, as it should be downgraded, but that's a completely different topic and not for this thread. I completed the entire campaign (except for mission 13) with the Sniper. It's obviously more difficult then, and better guidance with more data would probably be useful at times, but as you can see, it's possible to complete 12 missions with the AAQ-33 . Fortunately, we can rearm ourselves if someone wants to use more difficult optics ;). Cheers!

First of all, not very proficient in the harrier but i did fire mavs before and now like couple of days later i can't.. 1. master arms ON 2. Pick Mavs from STORE 3. double aft sensor select to get DMT running in TV ok.. 4. find target, designate so DMT stays on target 5. sensor select FWD to select irvm mode for mavs 6. lock the target as i aproach ever so closer 7. nothing happens i can't fire the missiles.. cant fire mavs.trk

I noticed that despite the fact that the wind is in the runway direction, if 25L/07R has the same ILS frequency, there is an interference, so I set up the "modern frequency for the 07R so it's fully usable. here is my beacons part of Frankfurt --LOC 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_20'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'RHM'; frequency = 110100000.000000; position = { -443583.906250, 100.000100, -851177.812500 }; direction = -100.841391; positionGeo = { latitude = 50.047996, longitude = 8.598907 }; sceneObjects = {'t:73852303'}; chartOffsetX = 4593.000000; }; --GS 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_27'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'DLF'; frequency = 109500000.000000; position = { -443643.500000, 100.000100, -851917.625000 }; direction = 78.659744; positionGeo = { latitude = 50.046376, longitude = 8.588953 }; sceneObjects = {'t:214099125'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_2'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FR'; frequency = 297000.000000; position = { -442648.875000, 128.143317, -844779.937500 }; direction = -101.576053; positionGeo = { latitude = 50.065653, longitude = 8.684068 }; sceneObjects = {'t:73862380'}; }; --GS 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_30'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'FFM'; frequency = 110700000.000000; position = { -444321.468750, 100.000100, -852673.437500 }; direction = 81.530965; positionGeo = { latitude = 50.039301, longitude = 8.580205 }; sceneObjects = {'t:214090990'}; }; --LOC 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_24'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IFSE'; frequency = 110950000.000000; position = { -444262.406250, 100.000100, -851914.812500 }; direction = -100.825012; positionGeo = { latitude = 50.040944, longitude = 8.590415 }; sceneObjects = {'t:73852304'}; chartOffsetX = 4222.000000; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_5'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FW'; frequency = 382000.000000; position = { -445875.125000, 90.751128, -863257.500000 }; direction = -118.128176; positionGeo = { latitude = 50.009882, longitude = 8.439541 }; sceneObjects = {'t:73828942'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_6'; type = BEACON_TYPE_TACAN; callsign = 'FFM'; frequency = 114200000.000000; channel = 89; position = { -443403.843750, 118.535061, -848339.000000 }; direction = -12.414079; positionGeo = { latitude = 50.053775, longitude = 8.637223 }; sceneObjects = {'t:215810048'}; }; --GS 07L { display_name = _('Frankfurt'); beaconId = 'airfield163_21'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'RHM'; frequency = 110100000.000000; position = { -444432.531250, 100.000100, -855199.875000 }; direction = -97.789724; positionGeo = { latitude = 50.034575, longitude = 8.546010 }; sceneObjects = {'t:212951504'}; }; --LOC 25R { display_name = _('Frankfurt'); beaconId = 'airfield163_28'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'DLF'; frequency = 109500000.000000; position = { -444506.750000, 100.000100, -855987.625000 }; direction = 79.143587; positionGeo = { latitude = 50.032752, longitude = 8.535441 }; sceneObjects = {'t:73846094'}; chartOffsetX = 4591.000000; }; --LOC 25L { display_name = _('Frankfurt'); beaconId = 'airfield163_29'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'FFM'; frequency = 110700000.000000; position = { -445112.812500, 100.000100, -856363.250000 }; direction = 79.197225; positionGeo = { latitude = 50.026870, longitude = 8.531721 }; sceneObjects = {'t:73835198'}; chartOffsetX = 4222.000000; }; --GS 07R { display_name = _('Frankfurt'); beaconId = 'airfield163_23'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IFSE'; frequency = 110950000.000000; position = { -445032.750000, 100.000100, -855591.500000 }; direction = -99.485803; positionGeo = { latitude = 50.028721, longitude = 8.542056 }; sceneObjects = {'t:212951505'}; }; { display_name = _('Frankfurt'); beaconId = 'airfield163_11'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'FFM'; frequency = 320000.000000; position = { -443411.906250, 118.986508, -847382.500000 }; direction = -101.576053; positionGeo = { latitude = 50.055115, longitude = 8.650293 }; sceneObjects = {'t:73862381'}; };

We finally got an update for the Iraq map Great news, and the screenshots look awesome! Thanks @BIGNEWY

Hi There I am flying the F-16C module with the latest DCS 2.9.19.13478 version. My system is Intel i7 with RTX 4060. The Joystick is Saitek X45. The issue is that when the Autopilot is engaged, the ATT HOLD and ALT HOLD mode does not work. The lateral modes works OK. I have a track where I activate the ATT and ALT modes. The flight path marker appears to stabilize but it keeps drifting in pitch. It neither holds the ALT or the ATT. Please see the track and let me know if I am missing anything. Cheers! ALT_PIT_HLD_NotWorking.trk

You might want to stop using the communication menu binding, and start using the correct PTT bindings, unless you have Easy Comms enabled and/or only fly FC modules. Easy Comms is going away, and the communication menu will not let you use the comms menu in the air for FF modules if easy comms is forced off in a mission. Cheers! Sent from my SM-A536B using Tapatalk

So last night, I experienced a glitch where I was going along the taxiway towards the runway. I tried putting on the brakes when I was about to turn for the runway. I couldn't. I checked controls to see if it was assigned to my joystick, and it was. This morning, I tested it again, and it worked. Did anyone have this issue? I mean, I hadn't done anything.

Two A-10s from RAF Bentwaters and an OV-10 from the 601st TACW overfly Sembach Air Base, West Germany. Circa 1985.