TOViper

@Machalot Good idea, I already implemented it! DONE 2022-12-03: Any screenshots of the kneeboard pages need to be updated to the new look of the kneeboard. There is one on page 380 in Appendix II. DONE 2022-12-03: It would also be good to add the instructions on how to set Time on Target and ingress Mach number when setting up a custom cartridge on the F10 map, from @RagnarDa's post here: I've done it in this way: null null

Despite the very small differences, I fully agree and changed that. The "yaw dampener"would be a very uncommon wording... thanks for this catch! DONE 2022-12-03

OB 2.8.0.33006 SP The AI aircraft which is lined up on runway 27 is not taking off. See trk: 2022-12-03_AJS37_Quick_Mission_Short-field_training_AI_doesnt_take-off.trk

According to manua, what "Option allows the master server to take a screenshot of the game session." exactly mean? The game session running on my computer, or what? What does it exactly do? When does it do that? For which purpose was this function made? Does the upload disturb frame rate? What if I turn it off? In any case, the label in the game is misleading to what is written in the book. Thanks for any hints

@Machalot@MYSE1234 Is this on the internal bug tracker already? Thanks!

Finally, after tiding up my hard disc and finding this & that, I found what I initially didn't find (because it has been placed in a different folder by GeForce Experience), the inverted flat spin:

This is still not working in OB 2.8.0.33006. When will it be repaired?

OB 2.8.0.3306 SP Caucasus When spawning in the air, and entering coordinates for landing base L1 (which is to be created since it doesn't exist in the ME), the distance and heading to L1 are correctly shown, but the waypoint indicator shows B1 when pressing L/MAL and not L1. See track: 2022-11-30_AJS37_L1_problem.trk

SP OB 2.8.0.33006 Caucasus When starting cold & dark on ground ("Take-off from ground"), I can - after entering the cockpit - enable SPAK even if battery is OFF and no ground power is ON. I bound the action "Autopilot SPAK/ATT" to my Warthog throttle controller FLAPS switch (most rearward position JOY_BTN23). See attached pic:

Hey Vettefan! How do you normally change your brightness and contrast knobs? With the mouse or with some other input device? It might be then the case that the controls got synchronized when spawning ...

Just tested it, there is still something wrong: Took off with Rb75. Jettisioned all Rb75. Landed. Re-armed. Then, sight gage IS active, but shows broken picture, and sight is not slewable. 2022-11-30_AJS37_Rb75_sight_gage_broken_after_rearming.trk

@Machalot, can you please confirm and put it to the tracker?

Confirming, works for both cold and hot starts. After seven years, its OK to have some luck

Last I checked (today): This doesn't work. The dial simply has no effect currently.

OB 2.8.0.33006 SP Syria The heading correction dial ("KURSKORR") - on the right side panel - seems not to have any effect. See attached TRK. What should happen IMHO is that when changing the magnetic variation with the "heading correction dial", the CI (and the ADI) should change. For this mission, for that date, the magnetic variation at that location in Syria is +10°. I am pretty sure that the knob - in the past - changed something, but IIRC it changed the standby compass heading (which would be totally wrong), instead of the values on the CI and the ADI. What I currently cannot figure out is if the knob must be changed on ground (e.g. in mode BER), or if it can be changed in flight as well. 2022-11-27_AJS37_KURSKORR_failes.trk

Hello Noiser! Do you have any track for us to look at?

Hi JG300_Papaye! One one hand this seems a very good idea, on the other hand there are so many small issues corrected, it will be much effort to accomplish. But I'll see what I can do. Thanks in any case for your comment and suggestion! Kind regards, TOViper

Yes, it seems so.

It doesn't count what I believe, its always better to prove something. I can say for sure for my rig I was able to solve the issue by doing these steps: Have DCS running Set resolution to 1024 Quit DCS (this was important) Remove fxo shaders and metashader2 Start DCS and let the shaders be re-build Enjoy WPN page in good resolution (better than some guys above said it should be, because IRL it seems the picture isn't that nice ... *checheche*... )

@BIGNEWY I found the issue, but it very looks like it is caused by how DCS works (or in that case not correctly works) with fxo's: .) I did empty the fxo folder and metashaders2 before doing anything .) Then I start DCS .) "Display resolution" in the SYSTEM settings was set to 256 .) After reaching the first mission, the fxo's were all created .) It seems the WPN page is then rendered at that certain resolution (in my case at the "lowest - bad setting" of 256 for a very long time since I fly the F-16, because I struggle with fps since ever especially when I fly with TGP and MAV's and using them in parallel) .) I then selected 1024 in the SYSTEM settings, but: The fxo's seem not to be updated anymore; I had to delete fxo's for each change of the SYSTEM settings. Ah, and by the way: I had to use the current OB 2.8.0.33006, since I update a few days ago. Side story: The problem with the crosshair is gone, I now managed to see the crosshair with MSAA set to OFF. Hope this helps someone out there, but at least I hope you guys at ED will correct this problem somehow (which drove me crazy). Thanks, TOViper

What I found out is that: .) The NVIDIA setting "Antialiasing - Gamma correction" has something to do with it .) I have to have MSAA set to anything other than OFF (e.g. 2x, 4x) in order to have the crosshairs visible correctly .) It has something to do with the fxo as well I will test more when I have the time for, but currently I cannot reproduce it, either the whole thing NOT working nor working (hard to understand, but I got it working, but didn't found out what was causing the issue). Once it got broken by changing the NVIDIA setting, I need to delete the fxo and start from scratch. This is exhausting.

This is a problem of setting MSAA to OFF. A track doesn't help, since the rendering of the screen happens on the client which is playing the TRK. The screenshot is a good representation of what is happening. Currently I am testing all settings, this will take a while.

Wilco & report back, thanks meanwhile!

@Scanfox: are you - maybe - referring to this thread her: https://forum.dcs.world/topic/168281-landning-po-bug/#comment-168294 TBH, I don't think so since the user is talking about the final approach, not the approach.

Hello @Scandfox! Can you please give me a link to the related post? I woul like to read further details there ... Thank you!