Leaderboard

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)

Ok, snowless winter is done and below you can see a sneak peek of it. I spent many hours adjusting the mod to 2.8 lighting, making sure target spotting would be possible. The REV2 will be published tomorrow, so stay tuned! I have some good feelings about it!

Fantastic job on the city, this map is going to be great. however, I really hoped Normandy 2 would address the problem of Normandy 1 having really bright green landscape textures, but those screenshots look the same to me.

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

@NineLine can your SMEs confirm that the implementation changed between M3 and M4.2+? Because M3 is pretty clear that the radar remains locked to the hmd until otherwise told once cued, and whilst I know defence organisations make some weird decisions, making it harder for the aircraft designed to be a dogfighter to get a lock whilst in a dogfight makes no sense even for them. Thanks

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."

...but they are not that hard

Here are the converted textures OV-10 Bronco dds Textures Contains: - converted textures for the external model, cockpit as well as liveries - new entry.lua Make a backup! You shouldn't notice any visual difference for the external textures and the liveries. You may notice a small difference regarding the cockpit textures, they seem just a tad less crisp to me but I'm not even sure. You may want to use only the external textures and keep the cockpit textures as png, you should still enjoy an improvement with loading times. Feedback would be appreciated since the devs are considering converting all the textures for the next update

If you recollect some of the earlier posts you will see that I described this problem way back in Sep and offered the .dds 5 files up for both the main texture file and the cockpit. My aim was to see if we could improve performance and It did indeed improve mine, significantly, but only one other person responded so I removed the link to free up space in my Dropbox. I still have that zip files somewhere if I can find it again.

Yes very true....but not in what my OP post reported...I only used the basic DCS game missions ie: AH-64D Instant Action, Mission or Training. No special tailored missions, no mods. Its not a game stopper IMHO, but its very noticeably slower than 2.7 (for reasons I cannot guess), I am not the only person experiencing it, and I thought it worth reporting.

DCS Normandy 2.0 Enviado desde mi RNE-L21 mediante Tapatalk

Hello Wags, BIGNEWY, NineLine, Yesterday I've posted at the thread below - regarding the SPOT / SCAN function for the AIM-9 in the F-16C. (As there are no news on this for quite some time.) As I recall : - I've written in a corteous and polite manner - used the already existing thread at the 'wishlist' - even when others sometimes suggest, it should instead be in the 'bug section' - not so much to your liking https://forum.dcs.world/topic/297187-f-16c-spot-scan-functions-for-aim-9-missile/ ... however, in a not so polite maner, my specific post was deleted in complete silence, without any explanation. So, as a long time loyal customer of yours, I ask: what was the issue ? Best regards, Pedro

Hi, we have been able to reproduce the problem. We have a fix, now it is under test. Thanks for reporting. Inviato dal mio ASUS_I005D utilizzando Tapatalk

If I understood your request to ED correctly, it is that they should stop creating useless things like volumetric clouds, rainbows and all that relates to realism and immersion to devote this to advancing in their updates just for people who think that they measure themselves and only fight with others to the detriment of a beautiful atmosphere? think of all those who prefer to fly only for the beauty of this simulator, everyone needs it I would have liked to wish you a good flight, sir, but I think you would prefer that I wish you a good fight.

@NineLine can this be checked again? The early access manual states on page 162/163: „Positioning the switch inboard short (less than .5 sec) rotates between three filter options: • ALL. All symbols are displayed • FTR+. Surveillance tracks are removed • TGTS. Surveillance and PPLI tracks are removed Positioning the switch outboard short (less than .5 sec) selects NONE and removes all datalink tracks. Selecting outboard short again returns to the previously selected filter option.“ nowhere does it say that raw radar hits/bricks are removed. Only that datalink info is being removed depending on the selected filter. currently (at least on OB) it doesnt even display the raw radar bricks. But it somehow detects them anyway since you can lock non-displayed contacts on the fcr as demonstrated in my previous track with a little help using the HSD. i believe the bug currently is, that raw radar hits are not being displayed correctly when certain filters are active.

I also feel it's very impractical, i'd love to know the reasoning behind such a thing. The way i see it and used it before this change was basically having the ability to direct my radar in a precise beam (The ellipse) with my helmet line of sight and catch any target my eyeball wouldn't see. It was useful when flying in the mountains and having difficulty actually spotting a target just under the 10 mile limit ACM mode, sometimes while slaving the ellipse around just looking i'd pick a target and therefore it would allow me to react instantly even if the target was 50° left or right. Now this would be impossible without using the HUD front scan or 10° vertical scan which are fixed facing forward, meaning any targets not directly in the rather small facing cone would go unnoticed by my radar. (Bold part : Who would go about constantly pressing TMS up while looking around to achieve the same result we used to have by just looking around and pressing nothing ?) Another aspect i find impractical is the simple fact that when in a dogfight turning around each other, it just felt way more logical to only have to aim your helmet sight with the ellipse on the target and let the radar lock as soon as possible (Probably faster than what we can achieve with the normal human lag ~200ms, especially considering sometimes the target would pass in that ellipse for a split second), rather than now having to either constantly keep TMS up until target gets lined up in the ellipse, or having to manually press TMS up everytime the targets falls into the ellipse, to me that just feels like an unnecessary step the pilot has to take when it could be done automatically by only looking at the target and letting the radar do its thing. The less steps there is to do something, the easier it is and more convenient no ? Here we are adding a step for a reason i cannot think of.

The problem is that the radar should remain slaved to the HMCS LOS until commanded to do otherwise, rather than revert to HUD boresight at the instant the TMS is released if it can't find a target. All publicly available manuals are clear on this. The Hornet works like that as well. And it just makes sense, especially if you consider that the helmet might be slightly misaligned which would make such instantenous function useless. If ED's M4.2+ documentation or SMEs say otherwise then I will be very surprised, but I can't challenge them. All I'm asking is that they double check they haven't missed anything, because I find it hard to believe it works like it's currently implemented in the game.

On the right - big red & white of the ejection toggles, to the right of that is weapons power, then the anti-collision beacon, then the 'gyro switch'. In the English cockpit it's labelled MH & MAN. You want to from the top position, down into the middle position. If you take it all the way down to manual, then rather flip it all the way up again before taking it to the middle.

So you're saying the 4.2+ handbook has a different process than 3 & 5.1 (which was previously shared here, but now deleted)?

It is in our To do list

Rergarding the fragility of nosewheel stering we have noticed that the static force where too low which caused always a suspension damage while breaking hard. We have improved it and will be available with next OB update.

It seems, from my point of view, the manual got missinterpreted by ED. They concentrated on the first part of the behaviour which is clearly "correct as is" (without the reported bug) but do not pay attention to the second part (Page 77 MLU M3 Manual). And the second part describes implicitly what should happen after TMS is released -> the FCR will try to lock within the ellipse (clear part) and if there is nothing to lock, will stay slaved to the LOS as long as no event of page 77 will happen. This part would make no sense, if you always have to do TMS FWD to slave the ellipse/FCR. And I can't imagine that this behavior has changed from M3 to M4.2 and then back to M5, as mentioned the post before.

Not quoting anything so hopefully my message doesn't get deleted. I remember reading that in the later tapes (M5), the logic was the same as described earlier in this thread in the M3 docs. The FCR stays cued to the HMCS LOS and radiating after TMS fwd has been released. So It would be very surprising that they changed it only for the M4.2+ jets...

Check out the latest Pop-up attack tutorial!!

Hello currenthill! In case you intend to create annother helicoter for DCS... This helicopter is on my wishlist: Hkp 4. (Boeing Sea Knight) Used by the Swedish Navy (Hkp 4B and Hkp 4C) and the Swedish Air force (Hkp 4A). For those not familiar with this helicopter in Sweden: In the Swedish air force, the Hkp 4 was used for SAR. The Swedish navy used the Hkp 4 for ASW and SAR. If I am not completely wrong, was most of these built by Kawasaki in Japan. Best regards: Otulf

Version 2.5.1 – beta release Added Changed Fixed DCS: To high panel shake parameters leading to SSA crashes

Another vote for toning down the green here… it needs to be a darker, maybe browner green.

yeah this is what i mean, it's about the intentions and the priorities that the actions taken so far reveal. the upgrades @Silver_Dragon enumerates sound great but shouldnt performance degrading changes be done after those updates, not before? Do you see what I mean? For some of us , these are game breaking changes. I wasn't even going to post, i was considering just not flying anymore good lord this is a comment and a half isn't it? i don't measure myself by competition. i like to compete because it's fun and it pushes you to be better. also, if we have these incredible combat machines, it makes sense to use them for combat. i said in my OP that i respect simmers who are there just for beauty and vibes. but to what extent to the detriment of those of us who actually want to fight in these fighting machines? i'm not saying rainbows and clouds are useless. i'm saying it they are revealed to be too high a priority right now, in my opinion, compared to fixing the already very suboptimal performance of the sim. if it turns out that i'm alone in this or that i'm just a tiny minority, at least i'll have voiced my opinion before i leave. i don't want to leave but i'm also not going to keep suffering 25 fps in VR on a multiplayer server with an nvidia rtx 4090, it's just not fun. i sincerely wish you a good vibey sim flight.

We will do our best to add the weapons bindings to next OB update

I am not going back to flat screen but putting DCS on the shelf and using other flight simulations that work very well with VR. It is all about MP for me and I can't fly MP in DCS or enjoy flying with my squadron mates in VR, so it is all over. Halloween sale was a waste of time for me as it is pointless me purchasing products from DCS at the moment due to bad performance in VR. Version 2.7 was reasonable but 2.8 is a burnt stake. Happy landings, Talisman

Hi everyone. New(ish) to DCS having used it for about 7 months, not new to simming in general. I thought I had a decent handle on flying through MSFS and X-plane but DCS has this habit of making me feel a little idiotic at times haha. It's so unforgiving, and there's so many things to remember. The learning curve with say, the AH-64, is just so steep. Having said that, I love it. Wading through Chuck's guides, constantly doing training missions, free flights etc, I feel that I am making slow but steady progress with the modules. To the point now where at least things like muscle memory with, say, the A-10 controls for example, is now there (I have the Warthog hotas, which helps). I'm also making good progress with the Viper, which is pretty intuitive in comparison with others. The Apache though...... Jesus. I still can't take off properly 100% of the time. It's all just so much fun though. So immersive, so time consuming, I really think that of course, bugs aside, it's a masterpiece of a sim.

I can't grasp the fact that the designers would downgrade a piece of kit in a newer block I'm not a betting man but if I had to bet I'd say ED is wrong here Would love to see the source behind this logic considering that ED uses publicly available documentation so it would clear things up imho

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

Oops, yeah, what you said. on the timestamp here couldn't see much shaking in the camera/HUD more than before when slowing down. Of course that's ground speed on the HUD not airspeed (unless that HUD was different in that way too). Unfortunately the other footage with speeds (the one with external views too), you can never really see a difference between the shakes as it were and it's usually slowing down doing a loop/wing over.

I just spent a suspenseful half hour following the instructions and getting VAICOM Pro back in working order. I want to express my sincere appreciation for the time and effort put in by the community to come up with a fix for the latest update to DCS. It is impressive to see how a group of dedicated users can come together and keep us up and running. With Hollywood hanging up his spurs I am delighted to see someone take up the reins to keep us flying. I don't have the programming expertise to contribute to the technical side, but I would be happy to donate funds to the group to keep this effort alive. Again, many thanks for getting a software fix in place!

Уважаемые разработчики! С учетом 40-бального штрафа от местного "ГИБДД" постараюсь быть максимально корректным. Актуальный на сегодняшний день DCS 2.7-2.8, безусловно, шедевр не только с точки зрения воспроизведения физики моделей ЛА, но и в плане графики окружающей атмосферы, наличия различной техники, широчайшей возможности редактора миссий/компаний и много другого. Потрясающие облака, реалистичное движение руками/ногами личным составом пехоты, красивые солнечные отражения (даже супруга оценила!) и т.п. достойно слов благодарности. Вместе с тем, не могу не задать простой вопрос, за который большинство форумчан раскритикуют в стиле "сколько можно!". Тем не менее... С Вашим блестящим (без преувеличения) продуктом я познакомился в 23 года. Мне сейчас 38. Дождусь ли того дня, когда увижу в анонсе очередного обновления фразу в стиле "проведена значительная работа по повышению производительности на средних настройках для среднестатистических компьютеров"? P.S. Искренне прошу не "лишать гражданства" пользователей участников форума DCS. Просто крик души от безграничной любви к авиации и к небу!

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.

Flying the same missions over and over with a new plane gets old bud. Without any long term cohesion to the missions doing the same old quick missions gets boring real quick. Actual campaigns are much funner, stuff that actually works and doesn't require somebody to dive into a mission editor to fix everything and having to learn to do that is annoying. I get people enjoy tweaking endlessly and are well versed in creating missions, I don't have time for that. So when I exclaim there is a lack of actual decent singleplayer content I am not saying it to talk smack, its a shame and makes me want to play something else when my time is so limited. Unless you are flying the few super popular modules in singleplayer good luck getting any decent cohesive content to play. DCS needs a dynamic campaign system yesterday. Unfortunately DCS needs so much other stuff fixed and added to even make that system viable. Without working ATC, decent ground vehicle AI, and a few other things it's not even possible for this to come to fruition.

I love this guy But bear in mind, Im am not biased on my GPU choice, if these cards have issues like stuttering or driver issues, I'll got 4090.

Yes, the performance hit with 2.8 is not limited to VR. The thing is, from the data I showed in the first post, CPU frametimes went up by 30% while GPU frametimes went up by roughly 10% at the same settings. So for people who run DCS at GPU limit, they only saw about 10% drop with 2.8, while those limited by CPU saw 30% drop. On a monitor with 100+ FPS, that's not even perceivable without FPS counter. But in situations where DCS framerate is limited by CPU performance (like heavy missions or MP), a 30% drop becomes very noticeable. VR users are also more often dialled with the settings near the limit of their PCs, so any drop like that will kick them out of the "sweet spot".

Per esempio quella postata da chromium è una configurazione del 2019 circa (dunque parliamo di una fascia media di quasi 4 anni fa ormai) che, VR esclusa, permette di far girare il simulatore abbondantemente oltre i 60 fps (e, ribadisco, con anche qualcosa di meno sono ottenibili risultati cmq più che soddisfacenti) . Che DCS sia CPU limited e che non sfrutti al massimo le potenzialità dell'hardware odierno è noto ma questo non pregiudica in alcuno modo l'esperienza di gioco (VR esclusa) che mi sembra l'aspetto essenziale della questione (e potrei citare titoli tripla A con "problemi" analoghi). L'equivoco di fondo è emettere giudizi sulla base di una versione Beta il cui scopo è l'ottimizzazione futura e non certo ottenere performance immediate rispetto alle versioni precedenti. Il rilascio di moduli (di cosa campavano nel frattempo?) e ottimizzazione (dall'originale Fighter Collection Simulation Engine (Dx09) si è passati ad EDGE (Dx11) ed ora si è in attesa di multithreading + Vulkan) sono due cose che, nel corso del tempo, sono andate di pari passo. Non si sfrutteranno al massimo le capacità dell'hardware ed i margini di miglioramento non mancano ma è un fatto che il simulatore è tranquillamente fruibile con hardware di 4 quattro anni fa se non ancora più datato (la 1070 è del 2016 ed è fra i requisiti raccomandati). Bye Phant

TACAN fix, GPS IFA (and radar PVU but that's not modeled) Flip to IFA and if there's GPS it will be fixed in some 10min.

I'm so, SO glad you guys are responding so well to feedback! This is truly looking like it's going to be perhaps the BEST map in DCS!

While AI sensors are a significant issue that needs to be addressed, the engagement range and fuel conservation problems are more because you're using a general CAP task I assume rather than Search Then Engage, which places range limits on the AI. Any remotely realistic mission would need to use Search Then Engage type tasks. CAP/Fighter Sweep/etc are for simple missions where you just want the AI to shoot stuff ASAP.

One more small extension: The SGSSAA can make the environment a bit softer. To encounter this, the following additional settings can be appied in nVidia Profile Inspector: [4 - Texture Filtering] Anisotropic filtering mode User-defined / Off Anisotropic filtering setting 16x Texture filtering - Anisotropic filter optimization On Texture filtering - Anisotropic sample optimization On Texture filtering - Driver Controlled LOD Bias Off Texture filtering - LOD Bias (DX) -0.5000 Texture filtering - LOD Bias (OGL) -0.5000 Texture filtering - Quality High quality Texture filtering - Trilinear optimization Off Theoretically the negative LOD settings can force to use more detailed LODs for objects as the default, hence the softness is eliminated and also the cockpit interior would be even more crisp. Unfortunatelly this can make the shimmering a bit more in the environment, but not so much. Personally I switched OFF the SGSAA because the small performance penalty, maybe I'll switch them back on if ED manage to iron out 2.8 or after implementing MT / Vulkan. But I really hope that in Vulkan they have the possibility to rethink the whole AA process to be as efficient as possible.

We had 4 aircraft out for the show, 3 as static displays and 1 that flew. The TA-4, F-4, and F-100 were static displays, and our Me-262 flew both days in the show. Wings Over Houston is hosted annually on the airfield where we keep the aircraft, and are more than happy to participate every year. Our goal is to get the Phantom back in the air, and once that happens she likely will go back on the airshow circuit. I don't know for sure as that is down the road, and we have to get her flight worthy again first.

L'A-10 è del 2011: DCS non sfrutterà al massimo l'hardware a disposizione ma dire che "gira" come nel 2011 non è qualcosa che corrisponde alla realtà. E ribadisco che, VR esclusa, anche con un PC di fascia media (neanche recentissima) non ci sono problemi di sorta. Bye Phant

С 1:00 если посмотреть, отличный пример как хотелось бы. Внизу приложил пример из полёта на высоте в DCS 2.8. Гамма 1.8, раньше это давало мне больше контраста и кабина всё равно была различима даже в мираже. В жизни тоже в солнечный день нужно потрудиться, чтобы увидеть что-то в тёмном участке. Почему кабина такая светлая даже при 1.8? В общем ставь лайк если бесит прыгание яркости) Tonejumper.mp4

Okay.. so i´m starting to turn towards the "this will be a really cool map" direction.