Leaderboard

I would have to disagree on this news letter based on my group opinions and talks we have had whilst flying on Discord and in game this week, I was and we all were all really excited for 2.8 and its moving clouds, but I would say 80% thought the patch was pretty lack luster after it broke so much and frame rates dropped for 70% of the VR users, it wasn't overwhelmingly positive at all once you got a few days into it and discovered all the introduced bugs, it certainly took the shine of it which is a shame for such a pumped up update. What we liked PG lighting which is awesome but our group thought it was a strange map to use for this and thought it should have been the Caucus, we know it will be introduced across other maps but the time line on that, well its ED it could take years. F10 map updates What we didn't like FPS hit, as I said 70% of our pilots have said in VR and none VR they have taken a big FPS hit online and some offline, I'm talking up to 25% reduction in FPS compared to 2.7. Module bugs- so many, its too many to list but lots reported here when I have looked CTDs (some are fixed with the patch) Then we get a small patch that fixed quite a few nasty CTDs which was great and few module items but also ignored some pretty major ones like the KA-50 cockpit language issues with mixed Russian/English cockpits and autopilot issue (all reported) this is on a module that never had any major issues. If your beta testers didn't pick this stuff up and report it, id dare say you need some new ones in your testing groups, we picked the KA-50 issue within 5 mins of flying it. I cant recall a time when our servers have been empty on weekends but so far Friday night (our servers big night) we have seen literally zero participation in our online missions, is this due to 2.8 bugs or a slow loss of interest in DCS as its performance declines slowly, I have no idea, but its the first time for a while I have looked at playing some different games for a long time as none of my Discord mate are around flying since 2.8 come out This is also the first time I have set up a duel install of DCS so I can go back and play the last 2.7 build offline for my SP missions with out the 2.8 bugs. Sorry this isn't a positive post, DCS is such a great game and I love playing it as you know, but for me its slowly dying due to a lack of focus on things need and not needed. AI updates - across the board mainly ground units that are boring to fight against. Lack of focus on what your programmers are implementing for future updates i.e. internal 3D modeling of systems on the KA-50 V3 sitting behind panels I wont see from inside the cockpit and don't really care too much for because I cant see them and wont use them, or animated Apache pilots getting in and out of the bird, there is much more these guys could focus on that is way more important than this stuff. Performance promises in updates that don't eventuate when the updates are rolled out. This stuff is killing DCS for long term players like my self, who are actively engaged in DCS and have been for a long time and try to be the best DCS ambassadors we can for the brand on our servers. Cheers

DCS Normandy 2.0 Enviado desde mi RNE-L21 mediante Tapatalk

Looking at the MLU_M3 document, the following is stated: "Slaving FCR ACM BORE without a TOI (FCR Not Locked On) When ACM BORE is selected and TMS-forward is held, the radar is slaved to the HMCS Aiming Cross LOS in a non-radiating state. The FCR ACM BORE ellipse is displayed on the HMCS at the FCR LOS. The radar is commanded to radiate when TMS-forward is released (Figure 6-33). The radar automatically attempts to acquire a target in the ACM BORE ellipse when TMS-forward is released. The FCR is slaved to the HMCS LOS until one of the following occur: 1. The radar acquires a target. 2. The radar transitions out of ACM BORE mode. 3. TMS-right with TGP tracking an A-A target. 4. The radar stops communicating on the Mux. 5. The HMCS LOS becomes invalid. 6. The HMCS stops communicating on the Mux. 7. A TMS-aft occurs. Note that if the HMCS LOS is moved past the FCR gimbal limits, the avionic system continues to try to slave the FCR LOS to the HMCS LOS even though the FCR gimbal limits have been reached." Current implementation appears to respect the first paragraph but ignores the second paragraph on the following page (pages 76+77)

If only the DCS devs cared to make a 10 minutes change to their engine: https://forum.dcs.world/topic/299598-trying-to-connect-the-individuals-that-made-the-performance-enhancement-in-vr-to-the-dcs-devs/

Salut les aviateurs! Mesdames et Messieurs, today we are walking around Paris. In Paris, more than 20 original objects have been recreated on the Normandy 2 map, including: Eiffel Tower, Arc de Triomphe, Champs Elysees, Louvre, Notre Dame de Paris, as well as the main railway stations, the hippodrome, and the underground metro. We tried to do everything so that DCS users could plunge into the atmosphere of the world's cultural capital. Notre-Dame de Paris Hotel des Invalides Palais du Luxembourg Pont Alexandre III Gare-Saint-Lazare Paris Gare du Nord @Magic Zach @Fred901 @DD_Fenrir and everyone who cares about airfields. Thank you! We have added 5 airfields (Orly, Deadland, Friston, Poix, Triqueville) and they will be in early access. We will add 5 and continue this work so that the total number of airfields will be more than on the Syria map. Today we publish screenshots of two of them. Thanks for the support! Orly (original airfield) Friston (regular airfield)

Hello, ok, so initially it was meant to be just a compatibility update but I guess I went a few steps too far with it. There is still some work to be done here and there but the release of the new version should be just around the corner. This time I'm going to include optional sweetfx settings to make the scenery even more vivid. Cheers!

Just saw this. Would love to hear some details. Baltic Dragon @BalticDragonDCS Replying to @SSerponi76 and @RAZBAM not full, but covering all the major things that will be included in Early Access. Harrier is going to go through overhaul soon, so I put the manual on hold until that is done. 2:07 PM · Nov 3, 2022·Twitter for iPhone

As of the last update the RPT will actually jam when receiving a signal.

Гораздо лучше. Бросить не доделав в состоянии " ну летает, чо еще надо", это в разы хуже просто хреновой ФМ у полностью готового самолета. Это в целом говорит об уровне отношения разработчиков к пользователям. По остальным, ну вот субъективно. Я летал в реале из того что в игре представлено на Як-52, Л-39, Су-25. Сравним только их. Элка очень даже ничего. 52 не похож вообще, с 25ым сложно, на каких-то режимах похоже, но в целом ОЧЕНЬ много недочетов по ФМ. То есть для меня сейчас уже 2:1 не в пользу моделей от ED. Причем тот же як и грач имеют в магазине строчки про профессиональную летную модель, которая что-то там максимально точно передает. И стоит Як 2500р. И при этом перспектив допиливания этих машин нет вообще никаких. Мне очень нравится МиГ-15 от белсимтек. Чем он хуже любого модуля ED ? Тем что нельзя предохранителем пощелкать на М-16, или что там ?

This comment got me curious, so I did some testing to see if I could replicate. I've been flying the Ka-50 since 2009 when it initially released, and I never touched the Heading Data selector switch myself since I'm fairly certain it was never modeled. I flew on the Stable 2.7 and then flew on the Open Beta 2.8, and in both cases the switch defaults to the up position, which selects Magnetic Heading. For those curious why heading data derived from a gyrocompass is more desirable and accurate than a magnetic compass, you can watch this video: https://www.youtube.com/watch?v=UvhooB--P2s. But in a nutshell, acceleration forces affect magnetic compasses in such a way that they will temporarily drift under certain conditions of changes in speed and banking turns (all of which incur acceleration forces on the aircraft). The amount that they will drift is subject to the latitude of your location, the current heading orientation of your aircraft, and the magnitude of your maneuver; and the direction they will drift is determined by the hemisphere (north vs south) within which you are flying. It appears that this switch functionality does indeed matter now in 2.8, and you will want to set it to the middle position (Gyrocompass) for precise and reliable heading data. I test flew the Ka-50 in Caucasus, Nevada, Persian Gulf, Syria, Normandy, and the Marianas. In the cases of Caucasus, Nevada, Syria, and Normandy, the heading drift was quite noticeable with the switch set to the top (Magnetic Heading) position, but rock solid when set to the middle (Gyrocompass) position. There was a little drift in Persian Gulf, and practically none in Marianas; but while the other maps were higher in latitude, the Persian Gulf was probably a result of it's lower latitude, and even more so in the case of Marianas, which is fairly close to the magnetic equator. (You can even compare the heading tape in the HUD to the backup magnetic compass in the center of the overhead panel) In two of the instances, upon immediate loading, the magnetic drift didn't occur until I moved the switch to the middle (Gyrocompass) position and then back to the top (Magnetic Compass). I'm not speaking for the Ka-50 devs, since it is the weekend and they are part of a different team, but I personally suspect this feature is still work-in-progress; the bottom line is that placing this switch to the middle position to enable the Gyrocompass to drive your heading data will result in the best heading accuracy and reliability.

This is the quintessence of what I have distilled for myself, from reading and listening to hours worth of pilot interviews, many of whom flew both aircraft during their careers: "An average pilot in a Tomcat is more likely to lose against an average pilot in a Hornet, whereas an expert Tomcat pilot is more likely to win against an equally experienced Hornet pilot."

Вы купили ранний доступ. Поставили бету - вы готовый, бесплатный тестер.

Человек всё-таки странное создание! Сначала все кричат, давайте быстрее выпускайте, потом-зачем так рано выпустили! Это же бета версия вышла(для обкатки и выявления багов простыми пользователями)! Если для тебя рано, переходи на релизную версию(Я, например, на ней сижу и жду) P.S. А падения ФПС в каждом крупном обновлении происходит, со временем всё правят

Understood about the 'slowed to a crawl' and will ask no further for a time. However from a content-creator's standpoint there are a lot of basically essential things missing from WWII. Mobile AAA vehicles being a huge one. It's a bit hard to create realistic convoys with no mobile AAA. Ju-52 transports would be nice, even if just static etc. There are minimal AI aircraft to help paint a compelling picture. There are a lot of irons in the fire across the board, but WWII needs some growth in the assets department - it's like painting with a limited palette right now.

A lot of things have slowed to a crawl, you can blame all hands on deck for Multithreading and all the bumps and lumps that causes as it is added.

By request of a few members I have put this guide back up. But please note OpenXR now runs natively on DCS TURBO and Reprojection work with the latest version of OpenXR Toolkit! You may be better off with the official implementation than with OpenComposite (aka this guide) If you are unsure, I would suggest to start with the official implementation first What is this? An early quickstart guide on OpenXR for DCS specifically for Windows Mixed Reality Headsets – OpenComposite. It is designed to bypass WMR4SteamVR and interact with OpenXR via this new method NOTE: Windows Mixed Reality Headsets are specific VR Devices such as Reverb G1, G2, Samsung's Super-Mario Odyssey etc. Some examples of headsets that are NOT WMR are Oculus Rift, Pimax, Varjo. There are ways to make some of those non-WMR headsets work with OpenXR but this guide is not designed for them This post is constantly updated so you don't have to read through 2 billion comments. The community has donated it's time, effort, expertise and countless hours of frustrations to get this to where it is today. If you have an issue, make sure to read this post fully before posting Why do I want this? Improved visuals and performance. The connection between Windows Mixed Reality portal and SteamVR is a performance bottleneck. It also consumes more VRAM. The strobe lightshow that are the DCS loading screens are a lot more Valium and a lot less Ecstasy How much performance and visual improvement is there? Depends a lot on your hardware and settings. Textures felt like a generational upgrade. For those who don't run reprojection, because of a different way OpenXR Handles frame delivery, gameplay has fewer stutters and is smoother. For those who run reprojection, OpenXR can reproject 45, 30 and 22FPS, instead of SteamVR's sole 45FPS What works and what doesn’t? Mods Reshade does not work but reshading can be done via OpenXR Toolkit (more on this shortly) OpenVR_FSR does not work. FSR/NIS Works via the latest version OpenXR Toolkit OpenKneeboard now works! Thank you VrNecksaver now works Reprojection It's currently not great. (Especially on AMD cards it’s garbage) - generally a bit wonky where there are distortions & strobing (eg rotor blades, WWII aircraft) but works. You are injecting artificial frames which guess. Clarity will suffer. If it was this easy to bump up FPS, every game would be doing this. It has made large strides since the first Alpha iteration where it just crashed. It’s 2022. I don’t want to kink shame. So if you’re into it, have a go. A version with better performance is in the works which according to devs at Microsoft might take weeks or months Shaders I don't run any! OpenXR, The Toolkit with Open Composite is a far superior combination that is designed to run together in unison. Especially with the latest release which can adjust a lot of parameters and even gives you fancy sunglasses. Shaders can be buggy, often break with updates and can have unintended consequences with OpenXR However! If you're into reprojection then there is a shader mod that gets rid of rotor shadows which solves the artefact issues in the apache It's easy! You need 3 things 1) OpenComposite Release 2) OpenXR Tools 3) OpenXR Toolkit* [OPTIONAL BUT RECOMMENDED], Sharpening Saturation and Contrast controls, Reprojection etc etc... Let's go! Instructions By popular demand: For the fast method you may be able to get away with only Steps 2, 3, 4 (CAUTION: The fast method is also known as the very slow method if you account for the inevitability of having to come back to do all the steps properly) 1) Clean/Repair DCS Start with a clean baseline and resolution settings You *must* start with a clean installation of DCS. This doesn’t mean a reinstall. Just thorough clean/repair and check. For standalone installation do this via the Skatezilla utility (link below). Do a clean and a repair, make sure that the checkbox to check all the files is selected and additionally search for extra files too. Don't skip this step unless you know you have a fresh and clean install Pixel Density inside the far right tab in the DCS settings must be set to 1.0 Please use the skatezilla utility. (This thread would be a fraction as big if everyone did the above ノಠ益ಠ)ノ彡┻━┻ ) 2) Download and install latest release of OpenXR Tools for windows Its here: https://www.microsoft.com/en-us/p/openxr-tools-for-windows-mixed-reality/9n5cvvl23qbt Tick Use latest preview and customise the render (the % is the same as SteamVR aka 100% for Reverb is 3100px). Set the runtime as OpenXR in the far right 'home tab' (if you don't see the option then it's good to go) Optional in the far right tab there is a [very purple] OpenXR demo scene you can quickly run to see if everything is good to go I recommend to Leave Motion Reprojection off/auto - but if you're into it then turn it on (P.S. Ignore auto. It is currently for MSFS only and behaves as 'off' in DCS) NOTE: You can leave the render resolution unticked, in which case OpenXR will decide for you what the resolution you will get, but it's unlikely to be 100% 3) Download OpenComposite It's here: https://gitlab.com/znixian/OpenOVR/-/tree/openxr#system-wide-installation - scroll down to 'System Wide Installation' and click download link titled 'OpenComposite Launcher' Extract the folder and put it somewhere safe (Desktop or Documents folder - but not inside sensitive folder eg. windows or program files) Run OpenComposite.exe (A small number people reported that they needed to right click 'run as Admin') Windows Defender has caused installation issues for some. If there are issues of starting in VR, Make sure it's not blocking OpenComposite 4) Set runtime to OpenComposite (Which connects DCS to OpenXR) - On first startup it needs to download DLL's. Wait for that to complete before going to the next step. NOTE: The app configuration screenshot below is post DCS launch. Initially, you will likely see a blank page. This is normal The application allows you to select which individual games you would like to connect via SteamVR and OpenComposite and comes with a built in update utility! Just run it every now and then to check for updates - Neato! 5) Make sure that WMRP -> Settings -> Startup & Desktop -> Automatic Start Up -> SteamVR automatic launch is unticked (Optional) My settings for WMRP are as follows, but you do you boo 6) Re-calibrate your headset by clearing the environment Then realigning via Mixed Reality Portal, SEATED, and with the headset in the exact same position and with the exact same posture and direction you intend to fly in. This really helps tracking If you already had an earlier version of OpenComposite installed, from now on you will only need to create an opencomposite.ini if you have a specific purpose for it. It goes into the bin folder. I have attached a working example. But I no longer use it - in the past it has helped me with VR controllers and mouse (to see all available options go to https://gitlab.com/znixian/OpenOVR/-/tree/openxr First DCS launch you will likely not see the loading screen in VR as the shaders are compiled. This will only be the case for the first launch. Be patient, or take the headset off and watch your mirror screen instead Enjoy DCS OpenXR Toolkit - (Do it!) 1) Do this only once you have completed the steps above and everything works. Failure to do this can cost you a lot of time. A lot easier to troubleshoot without OpenXR Toolkit 2) Download this: https://mbucchia.github.io/OpenXR-Toolkit/ 3) Install and launch 4) Launch DCS then CTRL+F2 (or whatever keystroke you've setup inside the toolkit - mine are CTRL+ALT Up/Down/Left/Right) the menu will only appear inside VR 5) If the game fails to launch after the installation of OpenXR Toolkit or it doesn’t work then please see here: https://mbucchia.github.io/OpenXR-Toolkit/troubleshooting.html#missing-visual-c-system-component 6) Optional: Try out TURBO mode inside the OpenXR toolkit. It may give you extra performance but this may screw with FPS/Frame Time statistics. So use your eyeballs to gauge the difference. Finally, I *Highly* Recommend staying away from ASW/Reprojection and instead using the OpenXR Toolkit to lock yourself to 55FPS for a 90HZ headset such as Reverb G2. Going above that rate will likely give you stutters unless you can reach the magical 90FPS mark. Doing so consistently is a fools errand. Even 4090 owners will get CPU limited in DCS Post Install Everything works; but if you are interested in getting every bit out of your new setup please see @edmuss tuning guide. The first post just like this one is also always updated Please read these additional requirements and steps that might apply to you Mbucchia's Tips can be found here and are excellent. I highly recommend reading them as it will give you understanding of what is happening and often encountered issues, which I have written about below https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html Don't use the in-game settings to increase Pixel Density, use the OpenXR dev tool. It must be left at 1.0 Because OpenXR is very new, you must have a fully updated version of Windows If you are able to render above 45FPS (or 50% of your refresh rate). Are really not into this reprojection business (unfortunately AMD Cards suck balls when it comes to reprojection/ASW) but are getting judding/rippling/stuttering. Use the toolkit to lock FPS to ~46. Dont be afraid to experiment with different FPS figures. The balance lies somewhere around 45-60FPS but YMMV - also you need to be able to actually render the frames you're locking yourself to But what if I am the kind of man who wants smooth game-play and also enjoys nausea inducing epileptic strobe lightshow whilst I fly in DCS. I got you fam! Just turn on the 60hz setting inside Mixed Reality -> Headset Display -> Frame Rate. Glow in the dark MDMA pacifiers optional, but are highly encouraged Are you seeing DCS through a fishbowl but you're not a fish? Try this: Some people have an old version of OpenXR installed. This is especially the case if you in the past have run MSFS and/or beta/early releases of VR applications and windows. For some people it refuses to update. If performance is bad, do the following: Remove all three apps (screenshot below) and install OpenXR Developer tools. Then navigate to the right most tab which gives you a link to install the OpenXR Runtime via the Windows Store (something that I could not find by searching the store alone) - Install that, don't bother with the toolkit and launch DCS. Once performance is confirmed to be better, you may install the Toolkit Nvidea graphic card holders disable hardware-assisted GPU scheduling (HAGS). This is especially the case if you run OpenKneeboard or any of the additional non-standard addons. Failure to do this can in some instances give you a penalty of around ~20FPS. The issue stems around multiple processes using Direct3D/2D concurrently AMD Card holders Navi and above. Work out your maximum stable clock speed and set the minimum speed 100-200mhz below that using Adrenaline Software A note about performance in OpenXR and why performance figures do not make sense and my attempt getting in front of 'tHe FpS FiGuReS aRe WoRsE!' Please see this: https://forums.flightsimulator.com/t/vr-reverb-g2-wmr-performance-motion-reprojection-cpu-issues-overclocking/497696/4?u=mbucchia TL/DR - Put down those FPS metrics and touch some grass. The only thing that matters is if you feel the performance is better. The only thing that matters if you see the visual difference P.S Jesus! Forget crypto miners, it's all you guys who have been buying up the 3090's A massive; yuuuuge Thank you to Jabbah, Znix, Microsoft's Matthieu B and his team for this work and donating their own time (not to mention their sanity answering our dumb questions). These guys are the hero's who are responsible for OpenComposite, OpenXR Toolkit and OpenXR it self

VMA-231 has EU pilot slots available. Take a look at our video to see what we are about. https://www.youtube.com/watch?v=NamuL5CDRKE I'm interested, what should I do? Join our Discord https://discord.gg/tawdcs or talk to me @Highwayman#4077 if you want to ask any questions or, you start your journey with us or by signing up here on our Main site

*** Disclaimer *** This mod is not done by me. Credit please find below I am not an Ace Combat player but I come across this video below and the plane looks real cool: Note: Credit goes to @Sanikkat Download link is in the video description It says it needs FC3 but I think you can fly it with F-15C only It is kinda primitive but it is fun Ah, I don't think I can carry a laser cannon...

I feared when downloading DCS World 2.8, the very moment it was downloading! "Please don't have a lot of performance loss" over and over again. Typically, I don't fear performance upsets from patch to patch, my system is aging......... a little....but since 2018 my 2080ti has served me well, and still does! However, we all know how the "major patches", can behave. And with that said, in 2D across the board with my 5800x3D and 2080ti, lost about 20/25% performance across the board, with the exact same settings I had before the update. Now I've been kicking around DCS World settings for the last 5 years now, not saying I am a Pro....but I'm definitely not a "newb". Visually, there is nothing to suggest the major loss in performance, moving clouds? No! Rainbows and Unicorns? No! Angels Halos? No, can't be! There were some mentions of terrain shadows causing it "Flat" or "Default". No, that couldn't be it either, "flat" was always more performance friendly than "default" but I don't think that is it, however side note: The "FLAT" shadows are doing really weird <profanity> now! so that's a downgrade form 2.7! So just kicking the setting around to see if I could find an outlier! Scenario: F-16, genuinely seems to do worse than any other aircraft after 2.8, that is, between the A-10, F-18, and F-14, for me anyways! NTTR map at Dusk, probably the easiest map to run performance-wise. Preface, I do not let my GPU run unconstrained, I have a G-sync OLED, and cap the frames at 60. This is a personal preference! So, I will not be speaking in terms of overall FPS but in GPU utilization! Generally, in this SP mission I built for myself, under these circumstances on the ramp, the utilization is relatively low, won't speak to 2.5 in this instance, but all of 2.7 builds, loading into this mission, or one similar too it, I'll be sitting around 64 to 68% utilization...........pre-2.8! Now...... 86 to 91%, pretty drastic! Like I said, this loss is across the board no matter the map and mission I have built for it! Turn off msaa 2x, which I always have it set too, Clouds from ultra to high.....85 to 89% utilization. Thats weird, never have I went from msaa to no msaa and seen a significant uplift in performance. Soo..... put msaa back on, that doesnt seem to be the issue, didn't gain much from it by being off which is a first! turned clouds back to Ultra, and then turned terrain shadows off all together! Again.....84% to 89% utilization. WTF is going on here!!!! I gained very little from that! Then I remembered! ED felt the need to effff with the cockpit shadows and make them......"more realistic" I guess? That and shadows on MFDS, the overall lighting! I am a total Graphics snob; I thought the shadows and lighting in the cockpit was just fine but that's just me. I always left Cockpit shadows on high for years, literally, never had a performance problem with that particular setting.........unless it was VR, then I'd lower that setting to low. Never had an issue with it in 2D!!! Again....pre-2.8. So, I reluctantly turned Cockpit shadows off to see if I would Gain anything There, Because I hadn't with the other three settings, other than a couple percent. Very Anticlimactic "BOOM" 70% to 73% utilization! Not an expert in Video Game Design/coding, that is to say I dont know <profanity>, but...........I am kind of an expert in DCS world on MY system! I would bet that their damn "upgraded" shadows is killing the performance really bad when it hasn't before!!! Maybe this is just the new "norm" and I have to buy a 4090 now?! I really hope this is a bug or a poor optimization of these shadows killing the performance! PLEASE ED, STOP WITH THIS NONSENSE!

Doing some performance testing vs. the Fishbed.

The city of Paris and its monuments are very well done! Congratulations ! I worked for a year in Paris and visited all these buildings and I can say that you did a good job! For Paris-Orly it is well done. For Friston it's not quite that. Friston was an ELG (Emergency Landing Ground) so no hangar and no fence around the airfield, just temporary facilities (tents, wooden barracks) and two Over Blister Hangar for aircraft maintenance. RAF Friston: In red, Blister Hangar

HARMs were changed not too long ago that EWRs would no longer appear. EWRs operate at too low of a frequency for the HARM's seeker to detect.

Unfortunately, as no public data exists, we cannot fully demonstrate that our model is realistic. This is the limitation when working on these kind of aircraft, but people have to put a little bit of faith on the dev teams otherwise a lot of aircraft would not be doable.

Пожелание: не ограничиваться только Хэлловином. На день всех влюблённых, заместо скелетов, вот таких сигнальщиц включите.

It's not you, or your CH pedals @Moxica I have exactly the same issue with my Saitek Pro Flight rudder pedals on rare occasions. (Didn't really took time yet to investigate and place a proper bug report here)

This effect is good gives a more dynamic look.

wow... I'm sitting here literally considering going back to pancake mode. I spend far too much $$, time and effort constantly jacking with VR settings. Seems 95% of my time has to go to optimizing, fiddling, testing, patching when I should be flying. And to be honest, by the time I'm doing doing ALL that, I've lost the mood... It's almost like "making it playable" has become "the game."

Win11, 4090. Terrain shadows to off = pretty much 2.7 performance except for the increased texture load times. Terrain shadows to flat or default 25fps loss over 2.7.

Неужели наш претензии должны быть в адрес разработчиков графического движка?

Hallo zusammen In der September 22 Ausgabe des Combat Aircraft Magazins hat es einen tollen, 10! Seitigen Artikel über die A-10C. Besonders interessant fand ich Tatsache, dass mit der OFP Suite 11 die Warthog nebst der GBU-39 SDB und der BRU-61 / A bom rack ein high-resolution display system (HRDS) bekommt. Dieses Display beträgt rund 11,6 Zoll. Hinzu kommt noch ein Second Gigabit Ethernet Switch (2GES). Das HRDS wird dann auch hochauflösende Bilder des TGP zeigen, welches die situational awareness nochmals deutlich steigert. Kann allen Warthog Fans diesen Artikel wärmstens empfehlen. Am meisten freut mich zu sehen, dass die Tage der Warthog noch lange nicht vorbei sind

Onestamente è quello che un'azienda di gaming deve fare. Indubbiamente non è un processo piacevole per tutti ma il comparto audio-grafico deve andare di pari passo col resto dello sviluppo. Se si smette di sviluppare questo reparto si trasformerà in un gioco sempre più di nicchia e quindi con sempre meno finanziamenti, fino alla potenziale chiusura del titolo. Tenere un gioco volontariamente visivamente brutto per avere ottime prestazioni su computer che hanno più di 10 anni di vita non è una scelta commerciale azzeccata. Inoltre la tecnologia dei PC sta avanzando a un ritmo esorbitante e non usare queste conoscenze solo per accontentare utenti storici sarebbe addirittura stupido, per fare un paragone è come se una marca di auto decidesse di produrre una macchina senza airbag, aria condizionata, infotainment e tutte le cose venute fuori da 20 anni a sta parte solo per dire "però costa meno della concorrenza", vi lascio immaginare quanto venderebbe. Ricordo che quando si è passati dalla 1.2 alla 1.5 ho dovuto cambiare computer principalmente per poter giocare a DCS ma è una scelta di cui non mi sono mai pentito (visto che il PC è molto utile per un sacco di altre cose), li per li non ero contento ma non potevo chiedere che il mondo si fermasse per me.

У вас тут беспредметный спор. Вы поставили бету, вы и есть бета-тестеры. Оттестируете, заявите о ошибках на форуме, их исправят и сделают stable. З.Ы. QA стоит больших денег. А тут и так каждый квартал "распродажи". Пусть будет так как есть, но будет, чем не будет совсем.

Another interesting data point for me is at 02:03, where the pilot performs the only almost horizontal sustained turn for a short time, so speed is stable there actually, and not just going through the range quickly. There, with a very subtle climb rate, G sustained is 4,7-4,8G I tried to replicate this as close as I could in DCS, with 86% fuel load (I figured, 2 minutes of AB would get me there at that point), and DCS value is different, overperforming a bit. So for me there is 5,4 G vs 4,8 at a slightly lower speed and a very little bit higher V/S For me this 02:03 moment is the closest thing to an actual sustained turn, even though it's quite short, but speed is finally stable for a bit, and not just going through the range in a single screen

It already happened and I guess I did know even before I started. I started flightsim with warbirds and never developed a huge liking for all this diddle diddle stuff in modern airplan. My current favorite and almost exclusive ride is the Tomcat and I wait hand wrenching for the Phantom. With the Apache there was this gunship 2000 / longbow nostalgic and the challenge to build something like the TEDAC controls. After the Prototyp was done, I lost interest. The hardware lies in the corner somewhere and I never came around to fix the encountered problems in my cad files. Maybe one of this days....

@exhausted, I read the Wiki article on the RR Spey, but I'm not sure what that means. As you wrote, the comment suggests there was maybe an issue with overtemping the compressor outlet or other equipment in the vicinity? Still, while compressor outlet temperature would have been high (thinking high hundreds / sub-thousand deg-F), combustion chamber and turbine inlet temperatures would undoubtedly have been a few multiples higher, 2x to 4x compressor outlet temp if I had to guess. So it wouldn't have been a material and cooling technology limitation, although material selection issue is possible. Regardless, this feels more an argument for "we could have extracted more thrust from the Spey, but were bottlenecked". But more thrust is more thrust after all, and the RR Spey's already had about 15% more thrust than the GE J79s, even with this compressor outlet temp comment. Maybe it's a semantic argument, but I'm more inclined to go with @r4y30n and his area-rule comment (as to why Spey-powered Phantoms were slower at the top end). The Spey was a physically larger (bypass) engine than the J-79. They drove more mass flow which required which required wider intakes and trunk. The Spey's were also toed in relative to the plan-view centerline to minimize impacts at the mid-fuselage "waist" and their thrust lines were angled even further below the profile waterline than the already noticeable angled J-79s. (See photo below.) Cross-sectional comparisons of a Spey-powered vs J79-powered Phantom would show the RN / RAF fuselage to be wider and/or deeper for the entire flow path from intake to exhaust nozzle. Spey-powered Phantoms had less optimal thrust lines (angled several degrees off their flight vector) and more drag compared than their USN siblings. The bottom of the intake is level with the wing's leading edge. But moving aft, and greatly aided by the white belly paint, we see that roughly a third of the Spey's engine diameter sits below the wing's trailing edge. If you've never checked out his various blog, Tommy Thomason is an excellent resource. A former aerospace engineer, for McDD, he does wonderful scale drawings and contour comparisons of various subjects. "As it happens, my first job after college was working for McDonnell Aircraft as a junior flight test engineer on the F-4K/M Phantom program." For his detailed comments on the Spey Phantoms, see: Tailhook Topics Drafts: The Spey-Powered Phantom Changes

Hello Gents, I stumbled upon a gold mine here! Im glad to see the passion we all share for the tomcat. I'm also starting a pit build. Im digging the 3d print route.

Привет. Не у одного тебя потеря FPS. У меня тоже самое увы.

It's a known problem, fix is ready and waits for next DCS patch

Point out to me where I have ever said DCS world is developing FF Land or Sea modules. All I have said is that land & sea is playing a part. I don't think doing FF warship modules is ever going to be practical. I think pulling 200+ players to man a FF warship module is an impossibility, let alone 3500+ for a CVN. I think the point is that DCS World is a game that could possibly bridge between Simulator & Strategy Genres. With Air being the Simulator part & Land/Sea the strategy part

@Snuten With wet runways you should always keep pushed relight button on your throttle. Page 145 of the Flight Manual (included in Docs) Take-off from wet runways Take-off from wet runways may result in compressor stalls or flame out due to ingestion of water splashed by the nose wheel into air intakes. To prevent such occurrences, following precautions should be taken: -Taxi at the lowest possible speed, avoiding puddles and water-covered areas. -During the take-off run and until lift-off, hold the “RELIGHT” push-button pressed. -Lift the nose wheel from the ground as soon as possible.

You owe me a new keyboard QWERTY & coffee don’t mix lol.

Да ну, JF-17 от Deka будет получше чем F/A-18C от ED. После апдейтов говорят что и Mirage 2000C от Razbam тоже весьма хороший крафт ничем не уступающий модулям ED, и даже в некотором смысле превосходящий. Стоит упомянут, что Razbam, например, не забрасывают свои модуля и допиливают их до совершенства, а ED походу уже забили на Як-52. Стыдно за такие дела должно быть... А, ну так это другое дело! Он не не законченный, он просто заброшен. Это кардинально меняет ситуацию!

Just got my Quest Pro. Have not got the chance to test it much, one hour or so with about 30min in DCS. More time to test tomorrow but my initial impressions are: Disclaimer: My only other VR reference is the G2, so that is what I compare it to. Pros: GREAT lenses, very clear. Cockpit in the F16 is as clear as the G2 but across the whole FOV - GREAT plus G2 seems a bit clearer when looking at objects in the distance. Better contrast, brightness and colors than the G2. Much easier to setup Good tracking Eye and hand tracking, don't know if the latter works in DCS (not tested yet). Noticed less eye strain. I could not wear contact lenses in my g2 cause my eyes dried up to fast. Did not notice anything here, may be since I didn't need to stare at the center of the display to keep the sharpness. Cons: Not very comfortable to wear, feel it pressing against my forehead. Not a game breaker though, just a bit more uncomfortable than the G2. Can easily wear it for a few hours, but might not go straight to the pub due to red marks on my forehead... haha Not ideal to use for dogfighting before the full light blocker is available.. Looking up and back at your six it will reveal your desk and monitors. A bit immersion breaking. On another hand it was a cool feeling seeing your lower arms sort of connecting to the VR model in game. Lost some performance going away from OpenXR, tried both Steam VR and Oculus VR, the latter seemed the best (I use steam version). Didn't notice much difference in FOV compared to the G2 which was disappointing. Maybe I notice it more when I try the G2 again tomorrow. Will test more during the weekend, but think it can be a really good headset with a better GPU (still waiting on my 4090) and a full light blocker. Also: Can't seem to disable the Oculus Anti-Aliasing and "Enable VR layers" settings in Oculus Link graphics settings. I press the sliders with my controllers but the slider won't move. If anyone has any idea how to disable these (or if I need to?) I'm not familiar with the Oculus software so please let me know Edit: typo

Я, как и многие не только в русскоязычном разделе, сначала бы хотел, что бы добавили нормальный кликабельный МиГ-29/Су-27/что угодно из 4 поколения красных, пусть и ранних. Тот же чистый Су-25 был бы актуален, как никогда.

A 2000-5F would be very cool (I'd throw money at it), but I'd actually prefer a 2000D with all the bells and whistles.

ED please consider adding at least Qatar with Al Udeid Air Base, it is a very large and important USAF hub with B-52's, B-1's, and KC-135's, along other USAF and Qatari assets deployed to there on various occasions, it would really add some great playability