I am just disabling the app in startup until (if) we get a working update. Very dissappointing that this bug has not been addressed. Beginning to wonder if FSR are going dark like many other developers leaving orphan products. I don't even mind if they are working on it, it's just frustrating when there is no feedback to let you know what is happening. Makes me wary of buying stuff from devs these days. w

this has been an issue since November, how about an update as to when it is likely to be fixed? Product is broken......

Thanks for that, I really didn't know what it was for, now it all makes sense. I'll give it a try next time.

yep looks like just a few minor issues listed in announcements section, which they will no doubt issues fixes for in due course, so all good as far as I am concerned now.

that is a brilliant idea imoh

looks like someone else has similar issue - see "Saitek Yoke binding not working" issue below.

correct. and verified as when FSR is switch off or not enabled in the first place, no issues.

after messing around with this I find that auto start works so long as you install away from not just in the programs area but also the boot drive. I installed in another drive and magically everything works. Presume this is a MS priviledges thing.

Just re installed outside program files still will not auto start, worked fine on 1.04. Isn't there something about if it ain't broke....