PiedDroit

Ah ok, it's not the same as the ILS one.

Cool, I thought it was 8 minutes no matter what (not counting memory mode).

Nah we can keep this one ;) If you forget it in your startup procedure then you'll have to wait in flight before being able to use it muhahaha. For the same reason the ground INS alignment time should still exist, but not be 0. Because you should still be penalized if you forget to wait for it to be finished before taxiing. I'd say 3-4 minutes is a good value (like in A-10C or Ka-50).

I find this request perfectly comprehensible (in the end I wouldn't mind it to be implemented). Ground INS alignment time doesn't bring anything to the enjoyement of the simulated systems. Having radar, ECM with detailed, real simulation IS bringing something. Here's an example: I would be OK to reduce the time needed to align the INS on the ground, BUT not OK to cut the time required to align the INS in flight (if it is ever available/possible, I just use it as an example), because with the latter you are actually doing something (i.e. flying the aircraft in a precise way to allow in flight alignment). You can call that "training value" (this term might sound familiar).

:thumbup: Other axis can be tweaked the same way (but are less important for True View), what worked for me is: TRACKIR_YAW: saturation Y = 43 TRACKIR_ROLL: saturation X = 49 Of course you need to adjust the gains in you TrackIR profile after that.

Great info in this thread :thumbup: I'll throw my 2 cents :D ILS glide slope is fixed and dependent on the runway equipment, so I doubt you can enter it manually. Also not needed to display a runway.

Bow ties are cool

I think that chart does come from a game. Looked nice though, but not very realistic (might be a mix for a generic Mirage-2000). The wiki page for the C only states "rockets" and "up to 4 pods" for the D. So I assume the airframe is capable of carrying them. This and the fact that "EXT" and "INT" ended up in RAZBAM's Mirage-2000C are good hints that we could have them. But nothing is certain...

It's not that bad, the gun cross and snake (even without radar lock) is still useable on short range snapshot. Longer range snapshot aren't a good idea anyway, you don't have enough ammo to play with so you need to make every shot count.

Yeah I don't know why.. Other sources say up to 10 GBU-12, which is more believable with the D.

Yep, after a quick research I found a couple of diagrams suggesting that the 2000D was able to carry the rocket pods in all 4 wing pylons, so it makes sense. https://en.wikipedia.org/wiki/Dassault_Mirage_2000N/2000D#Mirage_2000D "Up to 4x Matra SNEB 68-mm 18-round rocket pods on the four underwing hardpoints" (I know this data is for 2000D)

I noticed that too, forgot to post about it though, it's an interesting question. My guess is that you may load more that two rocket pods and thus select which one you want to shoot (if loaded with different types of rockets). I don't know where those additional rocket pods would be placed though. -> On magic pylons? Too heavy? -> On wing root pylons? What about rocket exhaust directly into the engine intake? -> On twin racks? I doubt they can command separate pods.

Good point. This is something to test when we have INS implemented. That is another topic. It's true that some server would benefit a timer for careless people who just takeoff, spam and pray then crash, but, this is not related to Mirage-2000C INS alignment simulation.

What's the point of this answer? It was elaborated enough already. Yes this is how it's supposed to work. And yes, you can botch your approach and catch GS first. Also yes, some airports have more than one GS transmitter using same frequency. This is starting to look like the proverbial dead horse :music_whistling:

ADI, and compass should be affected, I don't know how those systems behave when INS is not aligned.

It's possible IRL if you use back course, same frequency for both. However you can't use glideslope when in back course, only localizer. I didn't try in DCS though. Side note: glideslope frequencies are different from localizer frequencies. However we usually only dial localizer frequency because it is paired with a fixed glideslope frequency (that we don't need to know). That's why you can't have localizer and glideslope on same frequency for both runways, because you can't tune to another glideslope frequency and the glideslope transmitter work only in one direction.

That's how it should work, however be aware that switching to 530D won't deselect the special mode in current beta.

IRL it probably can (why wouldn't it? a glideslope antenna is no rocket science). The question is, how is it coded in the sim? I don't see the point anyway, in DCS with a normal profile you will probably get the LOC first. Edit: if you get the GS before the LOC, it's possible, it only means you're way out of the LOC beam.

It means you reach the inner marker (or outer or both, not sure). Edit: Page 61 of the manual, it flashes when the system detects Outer, Middle and Inner markers.

This and TacView :thumbup:

Radar is currently bugged as it retains the configuration (and damage) from previous flights, this affects replays as well (wrong mode will be selected, etc). You can try restart DCS and then replay the track.

Tssss that's very condescending :mad: - fictional? Really? The answer is probably "placeholder". What you see is a little circle representing the missile seeker's position (it also appears with the 530D). When you locked a target, the missile's seeker is on the target. That's it. This is not a "locked by Magic II" symbology.

What do you mean by "intersect - not capture"? The open box does not appear when you receive glideslope data, only when the localizer data is received but not glideslope (or you're not within 9 nm). And you can't place your FPM in that open box, as it is linked to the horizon. So, if I do a chronology, we have: 1- receive localizer => open box appears on the horizon, as well as the dashed deviation line. 2- receive glideslope, be within 9nm => closed box appear, anchored to FPM Edit: That open box gives the same info as the dashed deviation line. If you're right of path, that box will appear on the left, along the horizon line, regardless of your direction of flight (the waypoint indicator is giving you the direction to runway, not the open box) and the dashed line will be drawn from center to left, downwards.

They're not very bright, especially with panel lighting... Also, check this thread: DCS M2000C ILS

That's strange, those yellow needles are working for me :huh: I'll redo the ILS landing and take a couple of screenies, to check if we're talking about the same thing