Phantom_Mark

Well I flew this again tonight, with the view to creating the track, rather than fly the whole mission again I came in from a different direction and distance, seemingly no problems, having successfully completed that mission from the direction mentioned above I felt secure it should be possible with few problems, seems however it was maybe just the perfect storm of events to create bad results, no such issues tonight. Maybe the updates to the collision with terrain hit harder than expected, I was aware of those updates, but it never seemed a factor previously.

I read the change log before I even fired up the game, of course

So in both instances we are saying nothing has changed ? ok not a problem......I will make a track, just seems strange how I very rarely missed a thing previously and always shot the target I selected previously that's all. Hopefully the track will show what is going on so I can better understand that sudden change in perceived behaviour.

So I ran exactly the same mission last night, so have been able to compare back to back. Scanning an SA2 site and then selecting the tracking radar, then engage..............George either missed completely several times, mostly with missile and terrain collisions or when he finally did shoot something he shot the wrong target, not the one I had selected, he did that multiple times. 1: General accuracy seems worse than last Beta version ( I was using the K model ) 2: George doesn't engage the target you selected when there is a group I can't imagine this is my imagination as it is the polar opposite of my experience in the previous version, which almost made me wonder if they were too accurate ?

I was starting to consider this approach, just feels super bouncy /springy otherwise, everything else is golden now.

That was the issue, my axis wasn't quite fully into the fly position, meaning I was easily giving up maybe 7-10% of throttle, despite it looking quite close visually, since aligning it 100% I have had zero issues.

Since getting my throttle and collective fully and properly calibrated I have had a ton more success - the only time I drop out the sky now is due to really bad piloting, seems the throttle especially is super sensitive to not being scaled to "Fly" correctly. If I can just get rid of the rudder elasticity around centre and subsequent bounce I will be super happy

Which is why us clever game developers create AI code to mimic real behaviours, to try and suspend you in the belief you are in a real living, breathing, world.

Sorry if this is answered some place else..... The boxed blue edges seem denote overrides by the flight systems when you engage some of the AP features, but quite often I see the yaw/rudder being manipulated even when I am not using any of the AP functions ? Shown here is when I have radar height enabled, so an expected result is the that the collective becomes boxed by the blue edged box, prior to that the rudder was already boxed even tho I haven't engaged any systems ?

Well, I think I found a good part of the problem, beyond Pilot issues Looking over at the throttle it looked like it was nestled into the FLY position quite nicely, graphically at least. After messing with the lock out and observing the full travel of those levers it soon become apparent my fly position was actually needing a +20 curve to reach the full FLY position, I would estimate that probably equated to around 6% or 7% throttle setting below fly........could explain why I felt like I was dropping like a stone so often ? Just had a quick flight to confirm things and things def feel better, so that is obviously a step in the right direction, thanks for the tips....

I will get some tracks up at some point, but I am mostly focussed on the idiot in the cockpit at the moment, to try and self analyse if I am merely causing my own problems. One observation I have tho, which may be related. I was in a nice stable hover at around 50ft, deliberately trying to provoke the departure so I could better understand why and when etc, after trying to oversaturate the torque by using a ton of pedal to the left etc I resumed a normalised hover and then decided to have a little practice at lowering my height without excessive rotor speed, as usual I got Rotor Speed High warning and then started observing the engine percentage, it was sat around 45 on both engines, nothing out the ordinary there, as I am doing all these flights empty now so I can rule out the weight, then I started to enter a little bit of a vortex ring or ground effect , this was despite a very very very subtle and gentle descent rate, then it happened, I dropped out the sky like a stone because the moment I started to drop the engines were too slow to respond to my input, I visually saw I was going into a bad space and immediately went full power and added a little collective to get away from the ground........nada.......I will try and do it again but this but only increasing the engine speed next time ? I have no real issues flying around or hovering at all, its just these sudden unrecoverable moments where you fall out the sky like a stone...I have def identified my preference for circling left on a low approach & turn doesn't help, so that is one pilot induced risk reduced at least ?

I still love most of the aircraft included in FC3, the Mig29 , SU27 and SU25t being the ones I still fly pretty regular when the mood takes me.

I noted during my last flight the Sun was being rendered in front of the hills behind, never noted before, once you see you can't un-see I guess ?? Syria Map if that makes any difference, I am flying in VR here but the problem was noted in 2d as well.

Nope, normally the only time that throttle moves from fly is to boost the engines to get some extra rotor speed if it starts to dip below 95%, if if when descending I end up with high rotor speed and over speeding the engines - else it sits continually on fly, slightly OT it seems quite amazing there is not an automatic throttle which keeps all that stuff in unison / optimal

So I spent a good deal of time flying around empty in the same situation, just fuel onboard with gun rounds. 74% weight iirc. Most of my troubles seem to stem from trying to stop the chopper torque rotate to the right at low speed, basically just run out of rotor speed / and / or engine power , its the speed that it departs that makes it super hard to predict sometimes ?? the amount of times I have literally just dropped out the sky like a stone would defy the hours I invested and the effort I make not to create my own bad situations from bad choices. No track atm - maybe I make one later, and still as ever happy to concede maybe I just suck.

Also reporting in with this issue, running both normal and MT, 13900k Intel, DDR5 7600 Ram, with an RTX4090, loading from Samsung 980 Pro SSD's. Not timed it, but the loading times are significantly longer than they used to be after the last update.

Well, you of course have my support and best wishes, in the case of this module just seeing the fx lifted up to the same standard as other modules would be a good start.

So this isn't an official endeavour then, a result of your DIY stick ? I just upgraded to a Rhino - another stick born of the need to build a modern FFB stick, just like your project. Of course, in an ideal world I am looking for official support really, obviously what you are doing is very cool as well On a side note, given the work you are doing on these effects maybe there is something ED/Other dev teams could learn from your journey implementing this stuff ??

Well, this is music to my ears, which stick are you using yourself out of interest ??

So what you are saying is there is zero issues related to.........thank you.

I just checked, 80% weight I am starting to wonder if it because I have a habit of turning left at low speed rather than using the natural torque to turn right ???

Maybe, I tend to just have rockets and 8 missiles onboard ,nearly always this happens when I am at low speed either positioning behind a tree line or in preparation for landing, I find things go from super stable and predictable to completely out of control in an instant.

Gotcha, thanks, I have taken a quick look, might try and run it later

Even whilst flying with tons of consideration for rotor speed, vortex, and all the other stuff we have to worry about flying choppers I continually find myself dropping out the sky like a stone or spinning around wildly because I ran out of available torque because of the amount of torque being used by the rear rotor to remain stable or kick the rear to do basic turns, I don't feel this was so prevalent in the past ?? Is this totally just me or some of the improvements we might see in later flight model evolutions ? I know how the trim works and use it continually to make sure I don't run out of trim options

I completely understand FFB is not implemented, but all modules usually have like a default stick pressure value so the stick doesn't flop around - even if no other fx are setup, IDK how to implant these defaults but they are def a thing at least, if nothing else have you any info so I could implant those fx myself maybe ?