QuiGon

A new trackclip won't help if the camera is picking up background light! You need to fix that first, by either dimming your room (closing the curtains) or lowering the IR-threshold setting of TrackIR.

It's not mandatory in the F-16 either. You can use Mavericks just fine without boresighting them in the Viper. It's just that they will be slightly offset from the TGP, but otherwise they will work just fine. Pre-alignment (= Stored Heading Alignment) is something that can be done IRL. Boresighting Mavs not so much, so it wouldn't make sense to add such an option. If you want a fully prepared jet, there is hot start for that. I also don't understand the life time argument, as Maverick boresighting is something that's not part of the startup anyways, but something that should be done when airborne already (e.g. on the ingress to the AO).

Der DL-Schalter sollte aus bleiben, denn der hat in unserer F-16-Variante keine Funktion mehr (der war in älteren Varianten für den IDM-DL zuständig der dann später durch Link-16/MIDS abgelöst wurde). Wenn du uns ein kurzes Track Replay von deinem manuellen Startup zur Verfügung stellst sollte sich das schnell klären lassen

Thank you for reporting back that you got it sorted out and how you did it! It might helps others in the future

Besser als ein Video wäre ein kurzes Track File.

I can understand that, but imho in MP the server hoster/admin should have the option to decide what kind of realism level he wants to enforce on his server, so that he can ensure fair gameplay. In SP there is of course no issue with having the player decide what kind of INS realism setting he wants to use.

Then that's no desync as both crewmembers see the same. There's something else wrong then. Without a track file it's near impossible to fgure out what though, but I guess it's probably just some wrong radar setting.

Hmm, I guess you do indeed need to do the longer alignments if you have such high demands for accuracy. For me the accelerated alignment is generaly more than enough to be combat ready.

Nope, but shouldn't drifts be noticeable with normal PVU-800 WPs as well?

But the pilot does?

I use it all the time. Haven't experienced any issues with it since the initial issues after the release of BS3 got fixed

There are two options, one applies to cold starts as well and determines how the INS behaves. You only need to do a 3 min accelerated alignment in order for a combat rdy INS, even with the fully realistic setting.

Hmm, I have looked into the mission, but wasn't able to reproduce your issue. The hort starting Ka-50 always spawns with the B-13L rocket pod for me

The following is not my work, but should be pretty accurate: I hope this helps. If you have more specifc questions just ask away. I've digged quite deep into the Falkland Conflict and have quite a bunch of hard copy sources for it as well as contacts to ask around

In MP this should be under the control to the server admin (as it is right now), in order to be able to enforce the same level of realism to all players equally (if desired). But yeah, letting the players know what setting is in effect would be a good idea.

You're demonstrating the very issue with having a phrase like "minimum 2 nm distance", because then some users will think it works fine at 2.1nm, but that's not how it works. There is no specific distance at which it will work or not. It just depends on the distance you're using the seeker against targets in actual combat and the closer the distance you used to align is to the distance you use to lock up targets, the better the result. In other words: A boresight alignment against an object that is just 1.5nm away yields a perfect result in combat afterwards if you're using the Maverick against a target that is 1.5nm away. If the target is 8nm away the seeker will be far off though. Vice versa, if you do a boresight alignment against an obcet that is 8nm away it will yield a perfect result in combat afterwars, if you're using the Maverick against a target that is 8nm away. If the target is just 1.5nm away, the seeker will be far off. So giving hard numbers in the manual can actually be missleading, because there is no specific range, as it all depends on the specifics of your engagements.

Das wird ja immer merkwürdiger Hmm, solltest du dieses Problem irgendwie reproduzieren können würde mich interessieren wie das geht, bzw. noch besser ein kurzes Track File wo man das sieht.

Was hat denn die INV-Seite angezeigt?

Das ist es was dich an Aerges stört? Im Gegensatz zur Radarsimulation der Mirage F1 sind Model/Texturen erstklassig...

Bin ja mal gespannt welche Version des Starfighter es denn wird.

Jetzt auch mit Kommentar:

Works fine on my side. You probably missed something (maybe flaps not raised?). Can you post a track file, so we can take a look at what's going on there?

Ich glaub das verwechselst du mit Polychop.

Miltech-5 und RAZBAM gehen nun wieder getrennte Wege: