Toastfrenzy

Removing one file from the .miz file would improve the new user experience, along with the many others who use these quick missions, so worth doing I wouldn't doubt.

Removed some of the snapview.lua files that I found in the .miz mission files, tried the same quick missions and all good now for those missions. Do these miz files get replaced on updates? Or is it about time they where corrected at source.

Don't disagree at all for same control across modules. What about all the individual controls etc that are unique to individual modules (which I was referring too)?

Checked my snap view in the snapview.lua has a time date stamp of when I lasted edited yesterday - haven't changed anything today SnapViews["P-51D"] = { [13] = {--default view viewAngle = 91.992798,--FOV SnapViews["SpitfireLFMkIX"] = { [13] = {--default view viewAngle = 109.978734,--FOV

Really thought I'd cracked this - but no. Spent, again, literally another load of hours on this (and not enjoying DCS in the meanwhile) as its really frustrating having to set the FOV and or Zoom View axis up each mission or flight or have it change mid flight. Created this success video as I was jubilant at having resolved - albeit for 2 modules and used a couple of the quick missions whilst testing. Tried now (a day later) and the FOV zoom is different for some of the quick missions I have tried - it's still the same for the the 2 I used whilst setting up. Why is this and can this actually be prevented or is this just another accepted feature of DCS? I'm beginning to wonder if I'll ever get a session on DCS where by I'm not going to have to keep making do? I'll do another video showing all the missions with the FOV and will add later. The method how I've saved the FOV and Zoom view axis detent for both the Spitfire and P-51 I'll shorten for quickness; Head tracking off Show the Frame rate counter - Service info, double press to show FOV Adjusted View and FOV to where I want Save Cockpit Angles Zoom View - Tune combo Axis - select slider and curve - adjusted the mid 50 slider to reflect the correct FOV level and adjust the other curve sliders to smooth the curve. Making the midpoint 110 FOV for the Spitfire and 92 FOV for the P-51 Save On trying out this works for only some of the missions I've since found. I have tried selecting and deselecting under Game misc options - Sync cockpit controls with HOTAS controls on mission start - makes no difference selected or not. Couple of clips showing the different FOV's P-51 FOV set to 92 and Zoom axis mid detent is also set to 92 Spitfire FOV set to 110 and Zoom axis mid detent is also set to 110

I think JoyPro has made my controller worries almost nonexistent now. Still a little to configure but in a better place now anyhow. Thanks for all the help and positive comments, much appreciated

Dawn Bomber escort mission, doesn't go so well for E for Easy. I'm way out of position and a single snapper is all it takes, lose sight of the snapper then head for Manston for a touch and go before RTB. This ends up more touch than go owing to another new control bind fudge.

Sorry if I omitted that I did in fact download and have set up Joypro - a useful tool, that I've now spent the best part of 8-10 hours on over the last few days configuring and the like. Joypro is a good tool for sure but it still requires a certain level of aptitude, knowledge and dare I say it perseverance to workout why one keybind won't get exported when 50 will. It's a good tool for all the generic controls but for the Spitfire alone I've added 25 individual relations, not a complaint just an observation. Got the BF109, P51's P47, and both Fw's to do. I tried importing from DCS but it brings everything for the planes you select - whereas I probably only need 10-15 ish. It's another layer of "complexity" that in my view could be well avoided. In my simplistic view, all these controller "wheels" that have been re invented, as it where, many many hours spent by the community to improve a product could've (should've?) been undertaken by the source via feature request etc. Don't get me wrong, I'm fully aware of software life cycles, workflow priorities and the like. RnD and nice touches don't bring in the cash, releases and shiny things do.

Thanks for your reply @HC_Official Sorry but I do disagree with you there, it has lots to do with DCS. Customer satisfaction for one. In simple terms if I create a thing to work alongside another thing that's been around a few years and that thing then breaks my thing - whose responsibility is it to get my thing working again? I'll hopefully not make this post to you but to the general reader - nothing is personally aimed. Control assignments and their workings is possibly the number one general dissatisfaction DCS users have with DCS. Yes, we all have our own tastes and quirks but from what I've read whilst searching for help with my controller issues, lots of DCS users - who post - seem to have had controller assignment issues and or are taking very robust measures to avoid experiencing controller issues. Why was Joypro created? To solve a shortcoming in a bought piece of software. To cite some posts' I've read; you have taken a great deal of frustration out of the little recreation time I have looked at the start screen, realized I'd have hours of control configuring to do...closed the game Got a friend who wants to get back into DCS but can't be bothered to set up controls again (lol) Have been a fan of DCS for many years, however, have not spent many hours on it due to hotas setup difficulties. I am once again struggling with setup issues after convincing myself to purchase the F18 Hornet. Same frustration is emerging I know (somehow) the people who actually post, anything, online is a very small proportion of a user base - Take right now DCS forum 21-03-2024 1035 GMT Who's Online 193 Members, 0 Anonymous, 925 Guests You can be sure that even on top of those 1000, of those 193 members maybe 5 will post, there are lots more who don't even bother with forums etc for games. I had a discussion with my daughter just recently - didn't know some stuff and embarrassed\not confident to put her hand up in class. I said don't be embarrassed as you can be 100% sure at least 1 other person (if not more) will be wondering the same thing-got the same problem. Take a breath put your hand up and brave it out - you'll feel better afterwards and maybe get thanks, even a discrete nod of appreciation from others - in the same situation too. In other words don't just sit there and do nothing. I also said going round in circles trying to accomplish what should be a straight forward enough task is also like doing nothing as eventually you'll end right back at where you started from. I did reach out to ED and did get feedback that they are working on a control wizard to be released at some point in the future. To be honest with DCS, as a relatively new user had I the very short amount of free time I had previously to 12-18 mths ago I'd still be playing War Thunder 100% of the time. As that's a game - love it or hate it - you can pick up and just play. Now, if I can't dedicate a couple of hours then I don't even look at DCS. Fun fact; I stopped playing other flight sims back in 2013-14 and have 100% only played War Thunder until March 2023 when I felt I had the time and was ready to get back into some more serious stuff - I chose DCS - did I make a mistake - I genuinely don't think so, it's not been an easy ride more's the pity. what a post!

Got it, thanks @speed-of-heat

Not able to download JoyPro at the moment, it seems there's a problem with the Github repository or something. There's a problem raised (18th March) for unable to download any Joypro build.

Thanks, I've watched the video and GR even said "when ED bring out something like this......" I'll drop BN a DM see if there's anything in\on the roadmap at all for controllers and the like. I'll get this set up and give it a go - With JoyPro, how easy is to rectify new controller ID's as I experienced earlier,? I think I've spent more time in dev\testing\setting up than actually sitting down enjoying flying and "gitting gud" with DCS over the last year

Moved my PC from the cabinet to a desk as the PC just outgrew its home and rearranging the controllers before and after each time I wanted to DCS took its time. Configuring new buttons often means they get forgotten, a short clip of a slower than ideal take off.

Thanks! Wasn't looking forward to creating 3 x 5 module lua files for my 3 controllers - I'll just save the input folder as you've suggested. I can live with this at least!

Kinda surprised (?) that there's appears to be a lot of community advice here but no one from ED wants to jump in and get involved - all what has been suggested in my 2 forum posts works but they all involve things to remember \ some actions to be done. The one that I'll probably take away involves the least amount of interaction - not that I'm lazy but I know too many clicks becomes an eventual frustration in itself. Who'd thought back in the 80's that clicking a mouse in the 21st Century, too many times, would lead to a loss of sales! I'll save a copy of the C:\Users\%profilename%\Saved Games\DCS.openbeta\Config\Input folder as that will grab everything changed or not. Now I'm aware, I don't suppose I'll need said backup........

Hi, thanks for your time and detailed breakdown on my post. I'd be interested to find out the work required, ground up or a change. It's just that for me, if I didn't have to make manual allowances for maybe a coding issue and to have a system that doesn't require much of my intervention is a good place to be? I did realise that maybe quoting EAW (Released 1998) was a bit far fetched but I did have at one point, 2005 ish give or take for a few years, all CH Products, Fighter stick, throttle and pedals all USB and still no loss of sim key bindings. Any way the past is the past, looking forward..... For you it doesn't happen, now that's interesting. Do you save and rename the lua in the joystick folder or are the names you've showed us the default file names given? I haven't changed the default ones just saved some bad incomplete "profiles" to another location. But it's now on my list of things to complete after every Virpil button binding I change. No, it's not that unusual to save game settings, of course, but I've never actually had to use the saved settings in anger - only to revert back changes that I've made and didn't like etc. I would like to try unplugging one of my 3 Virpil controllers in to another usb port, to see again what happens, but I'm done with that now - - they are staying put!

I found a section for controller problems and bugs so I posted a question there May be a simple fix if ED want to improve another frustration thats keeps happening reading that section.

Having just fallen foul of this, my throttle, joystick and rudder pedals all being assigned new ID's after moving my PC and (perhaps) not ensuring that I plug them back into the same USB port. After which I went through a mild Oh no moment and inwardly cried. I made this post as I didn't find this topic first. Is this an impossible change to ask for? I've never had controller issues like this before even back with EAW - but I will happily stand corrected as that was a long time ago. There must be a reason why everyone is just accepting that this is the way it is, from reading all the many times it's happened and keeps happening to us all.

Thanks for all the help, the rename lua files was very helpful as most, 70%, of my button assignments were still present in the previous lua files. The missing 30% must be where I've saved the "profile" and only saved the rudder or stick but not my CM3 throttle where most of my buttons reside. I've recovered some and as all my controllers are still the "same" in the Virpil software (why not DCS) the hard work in button\axis to windows assignments are still present. I had recently moved my PC to another room https://youtube.com/shorts/QjzLXW6JPuE and never before had to worry about what port a particular controller was plugged into, as no game\software, as far as I can recall - even back to my early EAW days (lol) did changing the port a controller was plugged into bring up any issues. Just a pity that there are still these gotchas within DCS after 15 years of DCS being out there and also being one of the best of its kind if not the best. Not to bore - but I'll timeline my experiences since starting out with DCS last year. Started March - April '23 - took the 50% new start offer, couple modules, asset pack and Channel map ( securing new Normandy 2 map for 15%) New Normandy map released - logon issues for up to 3 days....as the demand exceeded DCS infrastructure capabilities July\August '23 After using for a few months my interest waned as cracks appearing with DCS just didn't sit right with me. Simple stuff - spotting for one. October\Nov '23 DCS 2.9 dropped. This was a revelation - brought me back into DCS the video description https://youtu.be/1ClI3X20GZU details all, for me at least. Dec 23 -Jan '24 New Virpil controllers, a learning time with Virpil software and DCS Feb '24 slowing down DCS as my room\desk situation with new controllers wasn't ideal March '24 PC move and "new" controller assignments issues, making me sad. Not as smooth as I'd like it to have been, I'll look to see if there is a ticket or something raised about the moving controllers issue, my gut tells me that this shouldn't be an issue as it is?

Just had all my controller presets reset to zero.......got all new Vipril gear (few months ago) and spent a lot of time configuring them and though not finished, far from it. It's been a worthwhile time going through the Virpil config software and then assigning within DCS. Each module has to have the same treatment. So it's a long process. Started DCS up to have a go today and all my (many) buttons do nothing. It seems my controllers have been assigned new id's - maybe, as there are now 2 lua's in some of the saved games\config folder, for a few of the modules. Not all lost but some modules have blank - default - lua's Where does the windows ID number originate from, firmware on the controller or usb socket association or some other random process? Anyway, something I didn't know is that when you click on the save profile it only saves the controller that is actually highlighted not the whole "profile" as it were. That's why my saved controller profiles are more or less redundant. I could be missing how to save controller profiles correctly for sure. But I now think I need to save 3 times at least for each module - Joy, Throttle and Rudder. I know this has happened to many - reading on the forum and also on other sites. What's the best way to keep this from happening - If it happens again I may just give up and go do something less boring instead. Also having FOV issues where I'm having to reset that all the time - there have been some recent YouTubes that have helped but the FOV seems to arbitrarily change itself on most modules.

It's happening to me and I have basically a vanilla DCS install with no custom mods and only SRS, Simshaker and more recently DCS nav (after the flaps started to flicker) apps installed.

I have a Buttkicker - I should think you need to use a 3rd party tool to get it to work properly either the Buttkicker software or Simshaker for Aviators

I had the TM TWCS throttle and TM16000m stick with no rudder pedals. I assigned L R foot brakes to the 2 left hand finger buttons on the throttle. You may want to try something like this? It worked ok and was reasonably good at keeping the 109 straight on TO with this set up. Though looking at the Virpil cm3 throttle I have, not so easy - maybe try the lefthand 3 way finger button - I have this set up for my Spitfire hand brake up - on & off - down and then middle press when taixing with rudder to get the left\right brake on & no rudder for both wheel brakes. Though rudder pedals will give you 100% control and it's so much easier (as i've recently found after so many years with stick rudder) - the BF 109 is a bit of a handful at first learning the TO - unless you've been there before that is.

Was just confirming the version shown when I run dcs.exe directly from the bin folder without using the created shortcuts that I normally use, shortcuts that bring up the MT DCS. Yeah, there's additional input that has added additional spurious complexity to this for sure! I understand KISS !! I'm also about to jump in and do some more set up with my new controllers, wish me MT!

What's the version you see when running from Bin folder DCS.exe? Just loaded direct from the BIn folder myself - same version level without the MT Preview text is shown So I'm running the MT version Yes, just confirmed running the MT version. Never tried in ST.