mrprime

This would be great, I play mainly in VR and have all shadows off but would gladly take the hit for internal shadows.

+1 also, as one of the few properly released modules it's not particularly encouraging to see the amount of regressions that are allowed to slip in and go unaddressed. In my humble opinion, regressions to released modules should block OB releases going to Stable. To that end, it's just daft that to get the F-5 to its released quality, you have to manually modify scripts or download mods. Make the F5 great again. Please also fix the texturing regressions: Range gate indicators have gone from the radar: https://forums.eagle.ru/showthread.php?t=245783 Various missing textures: https://forums.eagle.ru/showthread.php?t=270179

+1

I think this would be very toxic for the reputation of DCS. In F2P games, having very expensive high end content is referred to as 'whale hunting'. In games that have 'openly' followed that path, even where the 'whale' content is purely cosmetic, a lot of contempt is aimed at the developer for engaging in such practices, generally resulting in players abandoning the game and moving to others where they individually feel appreciated by the developer. Reputation damage is real, within the flight sim and gaming community in general, DCS would immediately just get meme'd on as 'that game that costs $500 a month and that doesn't even include servers'. It'd be a punching bag for toxic pricing and poison new players from visiting the game who might otherwise have given it a go. Also, considering the price point (and as you say, design) you'll have very few people buy in to that. Lets say 20 people dip in at that level, adding an extra $10,000 a month to the ED coffers. That's still really not big money, you could maybe hire 2 or 3 extra developers, which is great, but again isn't going to put an end to EA. However, that's not considering the loss of new users entering the funnel on account of the toxic pricing memes that'd forever be associated with the sim.

That'd be cool actually - a standard lightweight launcher where you could pick config, VR and anything else that generally requires a client restart.

Now that we have the DCS presets since the last patch (which are great! by the way), it'd be great to have a shortcut parameter we can set so we can load with a defined config, rather than having to open the game, select a config, and have it relaunch as it needs to restart for most settings changes. That would enable shortcuts that enable VR and pick a predefined config, something like: "C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe" --force_enable_VR --set_config_1 I know 'DCS Updater Utility' exists and I'm very grateful for it, but it'd also be good to have out of the box functionality to launch with a pre-defined config :thumbup:

As I recall for GBU-12 the correct fuzing is: * M fuze - 'OFF' * E fuze - 'INST' If you use those settings does the weapon become usable?

Welcome to you and the team! very excited to read the FAQ and all future news, insta-purchase for me!

Purely anecdotally from my experience, but as it stands right now, given equal skill and starting conditions, I don't see how the Hornet loses to the Viper in BFM. I find the Viper underwhelming in close, it bleeds crazy amounts of energy with light manoeuvres and despite it's stated T/W seems I find it next to impossible to pick up speed again without having it straight and level.

Oh man this is so much better - thank you! only problem I have noticed is that it seems to mess up the HSI's readability, don't suppose there's any way to make the HSI exempt from this change? that was the one instrument I _could_ just about see.

I get this the majority of the time I try and use the gun in multiplayer, I don't believe it's a network issue as it happens on any server (including self hosted) all of which I have good, low latency connection to, and experience no other problems. Recent example of the pipper going a bit mad during a dog fight, https://www.twitch.tv/videos/490252323

Same problem, have tried deleting Config,metashaders2, fxo folders from saved games\dcs.openbeta and still no joy. Was working fine prior to F-16 download. Update: Following steps in this reddit post solved it for me:

Now that the F14 supports custom cockpit liverys is it possible for this to pass IC? do we have to change the install path?

This is a nightmare, I restarted the cold start tutorial 2-3 times when it got to that section thinking that the switches had completely bugged out, can't find a good angle to reliably flick these - looking forward to a fix!

This seems to have gotten worse recently; I frequently do some 1vs1 duelling, and after open beta patch 4 me and the other F15 were surviving the majority of initial hits from Aim120 B/C's & 9m. I grabbed a clip off tacview - F15 survives 2 clean hits from a 9m; I felt like all of these should have been kills.

Same here, Thrustmaster T.16000m with TWCS throttle. Buttons seem to work, stick and throttle axis don't work at all in game - but do work in controller settings and bindings.