Hawkeye_UK

Confimed this is an issue both for MP (tested on both SDCS and DDCS) and Single Player on both Stored and Normal alignment. However cycling the GPS time off and on which takes a second on the DED page then enables DL - weird - @BIGNEWY@NineLine can we add this to a possible Hotfix please ?

Having to stop the whole game, reboot VR and come back in is a royal PITA especially when wanting to switch from Combined Arms or Mission Editior to "flying". I noticed last year on a brief review of MSFS2020 and a civilian module that you could as part of the base game switch whilst inflight between VR and monitor in the graphics settings. If ever there was core functionality that should be included, this is it! No more creating missions then having to reboot the whole game etc, or on MP servers where combined arms is required you can switch instantly betweent he two modes of play rather than having to leave the server, restart the game and come back in. Please can this be forwarded to the dev team for discussion, along with a technical response on if this can be done and if it can be added to the roadmap. Thanks.

just to confirm on further testing, i have tried all different attack profiles including late release and having the bomb come in at near 90 degrees. Same result no kill on these or the HAS style shelter we have in the Mission Editor. To note also the bomb will not follow the input paramenters for package solution.

confirmed and +1 this needs resolving ASAP.

Interesting, does this mean the map is being expanded slightly to the South given the new Airports listed, i mean Amman is right at the bottom, would seem odd to have a line of no terrain so close - Dead sea to be included?

APKWS - best TALD's there is

Has April fool's come late this year? Lets not have the repeat of the "team" stating such nonsense re JDAMS, its a similar discussion we had about the SA19 missile killing tanks front on.....(to be told its "accurate" then eventually corrected). We are talking about the M1 Scrum Half system here and non ER guidance kits. Also note specification and actual performance are two very different things, but an M1 system shooting down early JDAMS with the GPS kits is comical (without even considering the attack profile). Consider this, the system has been upgraded since the version in the game, in all aspects esp track to launch time, target saturation and telemetry. How many video's have you seen of non ER JDAM's being knocked out the sky in today's open source information (and rest assured it would be everywhere given the last 20 months).

Community finds another work around . Yea that sounds a good idea, stupid though really when its not a complex or time consuming fix from the get go (like every other controller in the game or module. Look forward to having to import every controls for all modules to 3 and 4, will give it another month and see if ED fix it first. Funny how the F18, F16 or basically any other module didnt have every other keybound lock. I hold to my original statement, the original implementation was poorly considered.

LOL it really doesn't break the assignments if done correctly - i have working LUA's lol and it did take me a few mins to do, once i'd figured out what the issue was. I don't understand your attitude on this one. Not everything is rocket science and i have no issues with directing people to improve their efficiency and output, not for one second. Instead of the protective closed approach you should really be thanking a fellow customer for an easy solution. If you want me to write the lua for you just let me know as i've already done it (via copy and pasting ED's own work). As for angry mob lol - i think even if (which they wouldnt) had to rebind many users would be happy to have the additional flexability to have the MFD's run things like the radio freq buttons and SAS etc on a modifier - happy to prove you completely wrong if you wish with a poll? Note every other module we have to bind MFD's, and on other products / Hotas. Are we saying that all these modules are poorly implmented and the A10 is correct, on your thesis? But mainly if i highlight issues with constructive critism, whether this upsets some sensitive developer or closed party tester is irrelevant its for the improvement of the product. You should embrace that and sucker it up, even if it means you are incorrect. I do the same.

Yea feeling that Retina burn in VR for sure......!

Hey Yurgon, Thanks for the response, i'm no PC whizz kid for sure however note simply copy and pasting the contents of keyboard bindable option largely to the thrustmaster "F16 MFD 1" and "F16 MFD 2" bindable option will remove the greyed out boxed and allowed them to be bound. I can upload the file if you need me too. aka take this file C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard and paste contents into C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\Aircraft\A-10C_2\Input\A-10C_2\joystick\F16 MFD 1.lua That is the "fix" this compares with how other modules are configured. I would suggest whilst im not great in computers - this is just a pure logic base problem and i can't even "write code". In summary both files can be "corrected" within 2 mins, so to be frank i stand by my original assumptions made. Yes testing will take longer for sure, however again to test each feature lets say it takes an hour (at the very maximum) - FYI i have already done this for you and it works. Note its an issue that should never have been an issue given a thoughful approach of how players use their button panels (aka with modifiers for second keybind) and lets not over dramatise a simple fix. @BIGNEWY Apologies re title but to be fair its been an issue for a long time, so much so i didnt want to raise closed bug that had been listed (or spend 2 days finding them). Sometimes consumer win's are easy, this is one of those occasions. I have Winwing and Cougars - if you need me to test then let me know.

Its a 2 minute copy paste job for ED - it should have been done years ago. I have gremlin in operation for discord - and the issue is it can and does chance devices sometimes (i have like 10 hardware USB's plugged in. So it far from ideal in itself as a piece of software. What im asking for is something that is only on the A10, and stupid to even have the locks in place anyways. Doesn't need work arounds - just ED to not lock pointless things down.

@Rudel_chwso im including the A10C - the A10C2 is literally a few extra things added, and the lua code for the thrustmaster MFD's is legacy from both along with 99% of the code, so yea its been a long time. Its an easy fix, and one that should have been done along time ago (esp pre ARC210 days so could use the MFD's to control radio's with a modifer) Buttons are locked so you can only bind the MFD keys on the cougar MFD's to the left and right MFD buttons in game. You cannot add anything else to them (greyed out in options menu) so for example if you have a modifer on your stick no secondary functions. If you have addional MFD's and the cougars become secondary button panels they are useless completely.

Guy's, I'm not going to route out the old posts, of which there was a few. Thrustmaster MFD's are locked to literally the left and right MFD buttons, which is insanity given with a modifer we still cannot use them for anything else. Also and more importantly as people (like myself) who move on from them to say total controls or the excellent Winwing MFD's these original mfd's would be extreamely helpful to be able to use on other keybinds, aka CMS panels, Stability controls, manual reversion, radio's you get the drift. Note people in the community have already wrote and made the change, however with pure clients on it will fail. Please can you literally copy paste the keybinds section into these and open it up for all - its very limiting and has been for along time! Why this was ever done in the first place god alone knows - its a mistake (its the only module also to have this). Please can you at long last resolve for all the A10 community with MFD's.

@NineLine Any chance you can pass this onto the dev team. The current F10 fog of war leaves alot of issues for MP currently and whilst appreciate we have many issues at present this is certainly one of them that would be a huge quality of life improvement for PvP servers. It would be welcomed by all additional layering and options of what is displayed.

Enjoying how the pre release map is looking - just want to make sure that pathfinding of ground units is going well? One thing to note is that the map really does need 3 or 4 additional airfields actually in the Sinai (i know more airports are coming but i dont think any are in this area and i can only see one in this whole area) to add depth for mission makers and to be able to create strategic directions for large MP servers. These being; Eilat (King Hussein International) / and - or / Taba International Airport Sharm El-Sheik Tor Sinai St Catherine International Airport Certainly Sharm El-Sheikh is a must in terms of providing that base and AO from the South.

Just be advised there used to be an issue with the hanger taking vram - its the reason why most people dedicated on VR remove this and have a blank and black hanger - also the reason why people remove their WMR home if on a G2 etc. or steam vr home back in the day.

can confirm tested and replicated. The hud ladder is particular troublesome and the release cues at night

Excellent thanks Flappie

AS PER TITLE. Please can you implement for both eyes, its not ideal in VR only having on one eye and im sure there are players that are also visually impaired. I remember when this topic came about regarding the Apache, Wags himself confirmed that all HMS will have the options for both eyes for this very reason. Poor given its such a simple thing and this has been missed.

THats another no...

LOL another month on and another month of an ignored post and problem. Its there any point to these forums - that is the question! What's the point in having an open beta if your not actually going to acknowledge issues when raised, or only those your interested in. Not good enough.

No response......again....

Bump due to nothing being mentioned in today's patch. Common ED....sort it out.

Why once again are the community having to bring out mods for things that should be part of any new feature release. Keybinds i mean common guys how hard can this be? When i loaded up on patch day i tried to find the switch settings to bind to my panels and couldnt - VR user. Toom me quite some time to release no they havent been given some obscure name, they are just not present. Why are keybinds so overlooked - CONSTANTLY! There are still many missing on the A10 from the original release and axis settings, let alone the new helmet sight. Same with new 16 features is the point im making. When are the dev's going to add Keybinds as part of a standard operating policy for any new feature in a clickable cockpit - as in a minimum release standard (please dont use Open Beta, hence why i referenced A10) https://www.digitalcombatsimulator.com/en/files/3319992/