Roostyla

The issue is that's not what is being said on various Discords by ED, we shall wait and see I guess for more official clarification of how this will work. I'm in the UK so don't have to work out my own tax lol

My understanding is that if you have not purchased the high detail areas but the mission extends to said areas then you wont see the buildings. So people with high quality are at a disadvantage when trying to use concealment (in a helo for example) . And the reverse if you have low detail you can hide inside a building that's not rendering for you but is for them. Or short hand is you get noclip and invisibility in those assets.

I was just about to ask similar questions to Ogma above, surely you gain a massive player advantage in multiplayer if you have not purchased high quality versions of the maps? Lots of potential here for customer confusion and double purchasing when not realising the savings when buying as an entire bundle. I think when you need an FAQ that extensive with undoubtedly follow up questions your not on the right track guys.

Thanks for the update BigNewy, we are chomping at the bit to get back into the 60 player action I'll share the details with my squadron.

Thump, reading between the lines across threads and discords the planned fix was for mid November but its taking longer than expected. Testing is being done on 4YA server but I dont think its conclusive yet. There is another open beta patch slated for December as Razbam said they have F15E patch ready to go for that. As a bit of commentary/feedback from myself and friends I think the bug was introduced 29.10.23 under 2.9.0.46801 . To introduce such a problem for this long and not only to choose not to rollback the beta patch but subsequently push it to stable I think is very poor decision making and doesn't utilise the purpose of a beta branch. I've stopped playing for the most part now aside from offline practice.

I have been a fixed wing guy for the best part of 2 years flying CAP for Helldiver on missions. Helo's scared the life out of me and looked super complicated but after a bit of convincing and a free trial I was up and flying with combat landings within a couple of weeks! Mando puts in a lot of effort with the training and documentation to support it and make the concepts easy to visualize. There are like minded individuals in the squadron that love to run drills and maneuvers and then take it in to PVP + PVE environments in planned ops and spontaneous flights. ECW and now Tempest and more. The more experience the better of course but don't be afraid if you are new to this, with a bit of dedication offline to master the basics you will fit right in. Pedals are recommended as that's what made it click for me in the Mi-8.

I'll give full flaps a go and see how it performs, thanks for the tip! I don't think i've changed my approach since the module came out. Normal loadout is 2 x fox 2 and a tank / 530 centerline.

Have you still got the autoexec file with command alt + enter fix from a few months ago? Delete that out as it will interfere with fullscreen being un-ticked. I'm not using anything custom anymore.

I use combat flaps or half flaps , decent amount of trim nose up. rotate gently at 150 knots and up she goes. Don't yank on the stick as that's when you will strike. There is a bug currently where the amount of trim varies spawn to spawn (at least on MP) from a lot of negative trim to neutral. make sure you check that as you will struggle if not trimming correctly.

Thanks for posting this Mole and highlighting something that got culled when the spotting 'mod' was brought the forefront of everyone's minds. The ban hammer came down heavy and locked down a bunch of mods that a lot of us used in the community . I wont go into that to keep focus on one thing at a time. I'd love to see it come back especially for the Mi-8 which you have highlighted which suffers awfully from dodgy shading / reflections. Hopefully it can be fixed for everyone or a option we can tick as its quite inconsistent module to module right now.

Just to add to this if you tried my earlier post and its not working, make sure to have open track / your software open in the background (don't minimize it) There is something about NOT having fullscreen enabled and having the app open that allows DCS to run without the stuttering for me. Still working in 2.9 . Yes you might be losing some max FPS by not having exclusive fullscreen but you gain in consistency.

Its a problem with other modules I think where it darkens a little too much to my taste but instruments are still readable as they can be back lit or lamps turned on. I'm new to the Mi-8, it's my first helo and the first thought I had was the same as Lasko that is was too dark to read instruments. Funnily enough I also used the same trick and had the flashlight on with the mouse cursor to read them! Try flying with dark clouds or even dusk and you can forget they exist . I was hoping to use the cockpit lighting systems as they are various dome lights but it didnt help much. I have since turned turn shadows to flat to remove the cockpit shadows entirely .

I'd just like to add that the issue of looking directly at aircraft and them being invisible , then looking to the side in peripheral vision and they pop in happens on 2D as well. I'm having to look out the side of my eyes to maintain visual sometimes. Within 2 miles or so. Longer range the dots are fine.

Adding a post for attention to this bug, It really helped with the asymmetric balance on cold war aircraft when the F5 gave a proper warning that an R3R was incoming , itgave players a chance to evade. It did seem a lot more reliable back in DCS 2.7 when I first played. Not sure what happened.

If you haven't already tried it then I recommend try turning off 'Fullscreen' and 'Vsync' in DCS . It made my head tracking much smoother and consistent, less stuttering / juddering . I don't understand why as it seems counter intuitive but there you go. Tested in MP severs Tempest and ECW, My other settings are PS3eye cam w/ opentrack 320 x 240 100hz NVCP Low latency - Ultra Gsync on Vsync on

Happening for me as well, 9b's were armed at the time. Did not observe issues with Magic 1s.

Good example Bucic, and I agree Mole. If the devs are intent on keeping it then a toggle option for adaptive brightness would be welcome or at least turn it down. What we have now really robs the game of the eye candy it can provide and washes it out, I already run a reshade ( luma and curves ) to darken and damper it down and even then its not always enough.

** ok i think I figured it out NVCP VSYNC off , Autoxec placed in config , in game fullscreen on and Vsync on (this is how we use to do it) . When game launches click the load screen. trying to alt tab does indeed lock the game and requires windows end task. Will test more on how it performs! Whats your Nvidia control panel set to do, VSYNC off , on or let application decide? I recall when were using this fix before we had to set it to one of those to prevent a black screen.

Ok ill give that a go later thanks for the tips, as for the topic in general your absolutely right Boosterdog, its been pretty much industry standard in gaming for years now to allow the user to select windowed/fullscreen borderless/fullscreen exclusive as that allows people the freedom for what works for them. However we had a jerry rig fix and even that got taken away. Surely cant be too complex a thing to create? Quick wins as they say in business !

@Boosterdog Hi , Nothing in my autoexec should i put the command back in?

I tried this method but i dont think its working , clicked the small load screen where it displays the version of the game and has DCS logos. In game I still see volume controls If i increase it. Can I ask do you have 'fullscreen' ticked in the options or not?

Ill give that a go this evening audiodistortion. Question for you, what's your method for verifying its true fullscreen and not borderless?

** tested, fix not in place yet, if you fly on ECW the Aim 9p and J are back so you can use those in the mean time, with the awesome un-cage! ** Hello, I checked over the patch notes and didn't see any for the Mirage, stealth fix maybe?

That's great to hear, I'll look forward to next OB update.

Just to add to this discussion I experienced this issue it too however with the magic 1s. In the F1CE I thought it might help to only load up with Magic 1s and no 530IR as that could of been the conflict (switching modes) I tried only entering Sidewinder mode once for the start of the engagements and that didn't fix the issue. I estimate it was over a minute before the seekers came alive and it should of been instant for a magic1. On the same topic on a different flight the 530IR should of been cooled as I gave it ample time however it was not getting any tones. I couldn't find consistency in it truth be told.