NineLine

Ok, so I did see it in your track, when I watched your track for a few minutes and then took control it didn't seem to switch in and out like yours, but it did seem to limit or mess up my TMS. So I took the same track but I took control right away. This time I had no issue. So I think first make sure something didn't go off with your bindings. It seems maybe like a binding or control might be messed up and maybe activating the TMS switch when you are not planning on it. Try there and lets see what you find.

Thanks for the track, I will have a look soon.

Aside from #3 which exists now, I have noted these with the team. Thanks.

Bug reports are marked as reported and ONLY closed when they have been submitted to the team to be fixed. Your '+1' does nothing to help forward the process and it only makes more posts for us to look at. Also: 1.14 It's forbidden to create threads/topics containing in their title/body: - hyperbolic, rude or strong language, also partially or completely masked by other symbols like @#$%^, etc; - no relation to forum section (flame); - no relation to the topic (off-topic); - please avoid low-effort posts like "+1", "me too", and similar (flood); - same information covered in other sections/threads/posts (cross-posting); - over 70% of capital letters for except for abbreviations; - non-informative content/titles like: "Help me!", "I have a question...", "rant", "I don't know what to do", "+=Super Pack=+" or meaningless set of symbols and letters. Titles or posts that break this rule will be subject to change or deletion of the thread/post. Repeated offences can result in warnings. As seen here +1s are against the rules anyways. So we cannot be any more transparent about bugs assigned to the devs than we are already being by saying they are 'reported' means they are indeed assigned to the devs. Thanks.

This should be sorted as the fuse work is completed as listed in the roadmap. Thanks!

As has already been stated, RAZBAM is committed to getting back to work on their products once everything is sorted. Right now there is no need to have any sort of disclaimers or any such thing right now as all that has happened was they have missed one patch. Lets let them work through it and we will go from there. Thanks.

This is already requested internally, thanks!

So I hide the posts from the point where I thought some of you lost the plot. This seems like the intent of the post was to be helpful to the community and new people editing or making missions. Please don't taint that by starting a debate where there doesn't need to be one. Thanks

Yeah there is a mod that does this sort of right now adjusting the global setting, or it could be done per module which would be more work.

First, Tacviews are no good for bug reports, Second, you have given no good information on the problems you are seeing. Please make a proper bug report, and I know you know what that means at this point. Come on skywalker22, you can do better than this. Third, this is an AI issue, not an F-16. Place it in the correct Core Bugs/AI topic. Fourth, no reason for the condescending and rude behavior, please consider this a warning for 1.10. See my signature for guidelines for reporting bugs if this isn't clear yet. Thanks.

Please see the road map. I know its take a long time, but the detail and work that goes into a modern-day pilot model is huge, and we do not only have the F-16 to do. That said it is coming very soon and getting very close. Thanks.

There will be more info when the feature is closer to completion, so please keep your eyes on newsletters and changelogs, it will just get lost here. Thanks.

This has been requested internally in relation to some of this, some of this might be not so appealing to the masses. Thanks.

This has already been requested internally along with all sorts of new effects. Thanks!

Not sure I understand your question. Sorry.

Guys, this is not helpful. One this is the Spitfire section, Two, you are showing examples like the Su-27 one above that is flying well over G limits. You still need to fly the aircraft within the limits of the aircraft... within reason of course. I mean the F-86 example above is just off the wall. So please, make reports in the section they belong in and make sure you are flying within realistic limitations of the pilot and aircraft you are reporting on. Thanks.

Fatigue is currently built into the model, so you should see less resistance to Gs as you continue on. I clearly show in my video above that there is in the Spitfire. I am not saying it's impossible that there are not issues elsewhere BUT this is the Spitfire section and you should include tracks as well. Thanks. Also in the examples above I did look at you are pulling well over the restricted G limits, so you need to understand that the G warm-up isn't so you can pull more Gs than allowed but rather that you can get up to the max G a pilot could pull. If you are blacking out you are pushing too hard, so much so that your pilot is immediately incapacitated.

So chatted with the team some more on how it works, did some more testing myself and even talked to Mr Grey about his experiences prepping for a display and if he had ever G-loc'ed. So the current system, even for WWII requires a warm-up, even in WWII. Now this doesn't mean you need to do a special maneuver before combat because you don't always know when you are going into combat, you need to ease into your first half-turn. So basically instead of going hard on the G's enter the turn 3-4Gs for about a half turn then ease into your max turn from there. I reflew the first track here using this method, although maybe not as smooth as I would have liked: For the sudden blackout, per Nick's experience he has G-Loc'ed twice he said it was 100% instant. His routine for warming up for a show is this: I will check out other tracks here soon. Thanks!

It does seem like a little too sudden to be natural, and I hate comparing the F-16 and Spit so directly, but I will see what I can dig up on how the system is set up and how WIP it still is.

Ok, I only reviewed this track so far, and I don't think that I saw much of an issue, I mean the screen does grey and then a short time later you are G-loced, I will ask if its expected to be more gradual into that, but as I have never personally passed out from High Gs I will need to dig deeper. Luckily we have an aerobatics pilot on staff

The key issue was that we had the new more dynamic reflections as well as the old static ones together on the F-16. The old static ones were removed and while you still have reflections they are more muted than before. We are still tuning as well I am trying to get a 'slider' so users can adjust based on their preference, while some here want more, there are others that want less. So a user setting might be the best bet. Thanks.

Actually fixed internally just didn't make the final merge, sorry guys. Shout out to @baltic_dragonwho flagged this earlier.

This thread is about what is in the patch, not a discussion of what you were hoping to see. As with all bug patches, we put in what we have. If we don't have something it doesn't go in. Sorry. Note on Sinai, they are working on an update right now, but it was not able to make this patch. So look for that coming soon.

No worries I just wanted to clarify as I am in the trenches on the issue

We are still working on reflections over all, so any updates or tuning may indeed be first steps depending on the module. Thanks.