Phantom_Mark

Any reason why it has to do it tho? I mean everything screen it draws to "costs" something, and as performance is already hobbled in VR to some extent why waste it drawing to a monitor I am not even looking at ? Anyone tried to disable it ? is there a way ? :book:

Daft question, but is there any good reason why we need to have the game rendered on our 2d screens when we are using VR ? I am sure there is a glaringly obvious reason, but it seems a waste of processing cycles drawing something on my monitor that is already being rendered in the VR screens ? :smartass: Is there any way to hide the monitor output while you are in VR ?

F18 has wing flex, maybe others as well, not paid that much attention to be honest.

Typically tried it tonight and the groundcrew not placing the covers etc...trying to see what formula I found that induced this little bug :D :doh: :pilotfly:

Will sort one out tonight for you, np.

Fingers crossed then, I seem to recall armour values were adjusted recently ? maybe that is why the Rockeye doesn't feel so effective now, just been trying dropping them in pairs instead and getting better results as I guess you would expect.

Previously I have found the Rockeye quite reliable and easy to use, especially using the weapon at 1500ft .........lately I have found I am having very little success destroying Armour with the Rockeye's ? Is this correct ? I also found CCIP in general seems to have taken a little dive in accuracy tbh ? even with regular 82's they seem to fall long.......something which seems to happen on other aircraft as well using CCIP ? Never had any problems previously tbh ? Always found the F18 a nice easy platform to use all the weapons with.

So if you land then wait a while after shutting down the engines etc the ground crew place the air intake covers etc and the other ground safe pins etc show up on the plane, you can then re-start the engines and take off with all the ground safe features still visible.......

So today's interesting lesson. It isn't just the FFB stick which lags btw......that's one discovery. Secondly, I have no lag at all on anything when I play in VR with my Rift S........seems I only have lag whilst in the air and whilst playing on a normal screen. The above scenario is repeatable time and time again, so found something solid to work with thankfully. I run my VR with the same settings as I do on Desktop......very strong system here, 5ghz 9700k & RTX2080ti Extreme Auros OC, 64GB Ram

So the MSFFB2 for me behaves perfectly elsewhere, and also the effects in the Tomcat work perfectly including force trim and shaking etc. I have been working really hard testing this module to try and define exactly what, why and where things are going wrong, done hours and hours so far but starting to narrow down some important facts than I hopeful will provide a lead for someone to look into if they are willing. I will publish my points at the end of the weekend, already made some important discoveries. Just for the record I love the F14b and really appreciate the hard work that has gone into it, it has only been my frustration at not being able to play with it properly recently which has caused me to say anything negative, I do feel Heatblur could at least be a little more forthcoming with customer support, even if I am customer with minority equipment, it is perfectly working hardware with only problems that appear in their module.

If you have a FFB input device I advise you give it a miss sadly..developers seem uninterested in looking into huge input lag among other FFB related issues.

Input lag is back with a vengeance, worse than ever. Can I respectfully ask the developers to at least take a little look please, the plane is currently not flyable like this :( I have tried replicating my previous posts to no avail. :(

This I can wear, and understand, thank you.

Sorry, just so we are clear :D , the damage model is awesome, no doubts about that whatsoever, it seems to be more so when hit by machine gun fire and stuff like that, light weapons feel like they are just chinking away at a hit point counter linked to available engine power, where the more serious hits seem to be reflected in proportional systems failures etc?

Really are full of yourself aren't you.......always ready and willing to learn, but frankly when someone starts playing the smart arse card my ears close, I have flown for real myself as well, so I don't need talking to like a 5yr old, thanks anyway :pilotfly:

Does the A10C use an overall hitpoints tally.......been flying this thing years and kinda just suffered it but just want to ask...... The engine power drops progressively each hit you take, feels very canned, and it assumed every extra round you took just happened to hit the engines, and just happened to reduce power output by exactly the same amount every time ?

You never live long enough for more than a 7.62mm worth of damage at the moment, so don't worry about trying to fly around battle damage :D :D :D Looking forward to seeing the full damage model, the A10C is a joy to limp home after having the crap knocked out of it :D

If you have flown a real one then I am all ears, if you haven't your opinion, like mine, is subjective :) :thumbup: I am all ready to grow ears and listen to how the real one handles on the ground compared to the version we have now.

Not sure how many more times I have to type this, there is zero wrong with my controls, nothing at all.....I can see this with the controls overlay that yaw is taking place with no input from my controls, thus no deadzone or curve is going to fix something that isn't being induced by my controls ???? and the rudder is spot on, never an issue, however when taxiing or parked I have observed the left rudder twitching at a high frequency despite the right rudder remaining static......which is clearly "odd" Thanks again for the comments on possible solutions, but I am firmly believing there is something going on outside of my control, and it feels like either the tracking is off on the wheels (alignment) or there is influences from the physical world being exaggerated beyond the norms. FWIW I have been flying DCS since Flanker 1.0......so done a few thousand hours in various types over the years and know how to setup my controls and taxi, not a boast, just saying, I would be the first to admit it is easy to overlook something but as far as I am concerned I have covered all the reasonable bases so far in eliminating me and my controls from the factors involved here.

Cheers Don, and others, good to just check we all fly from the same page.....a curve won't help my problem tho , as the plane is moving around with no input, the nearside rudder twitching makes me suspicious, anyone else replicate that whilst taxiing below 48 knots ? (not tested above)

That would imply the rudder is having unintended authority......which I have already ascertained it doesn't ?

Yup same, hence I made a mission with 0 winds etc to test....... :pilotfly:

I don't want to add a curve to the rudder as it just hides the problem tbh, and I have no problem with the rudder at all.......

Fingers tightly crossed mate, quite happy sit back and wait however long it takes for the rest of the module to mature once that feature comes along...... :thumbup:

The only thing the Hornet needs to improve A2G effectiveness 10x fold is that HUD marker for where the pod is looking, could we have some idea when that might appear, far more important than any ground radar IMHO, would make engaging TOO 1000000% easier. !!!!!