CrashO

Does anybody know a way to add paint to the body part of the nozzle? (not the split end). I haven't seen it on any of the livery's here (all of them use metalic nozzles). Because changing it in the tail texture does not change anything on that part. It still uses the metallic texture from the textures zip (I tried overwriting it inside the zip and it worked, but I want to do it for a single livery, not all of them :) ). Or was the painted nozzle only part of the NF-5 and not F-5? :cry: (I have seen it on most Dutch NF-5's and the Turkish ones, but not on F-5's).

Can't wait :notworthy:

So i'm not sure what is going on here.. but since last week, I have had several occasions (on servers like 104th and TAW) where the settings forced me to start unaligned (my preferences have always aligned enabled, but if the server forces it on me for realism, The lazy guy I am, will just takeoff with faulty navigation. So, so far, everything is just as one would expect. Alignment is required by server settings, I skip it and just take-off. Taking the lack of INS precision (if any) for granted and generally having a HSI pointing 160 degrees the wrong way. No problems there :D However.. in cases where I do want to navigate, I intent to use the emergency (magnetic..) compass . And what happened? It showed the same deviation the INS had. And what makes it even more interesting, after I entered a waypoint using its coordinates (Bullseye on the screenshot). The needle on my HSI pointed straight at it when flying towards it. And while all of the instruments where telling me I was flying somewhere towards 344, right towards the bullseye. I was actually flying east (right towards the bullseye).

To add to the list :smartass: - If you hotstart, the taxi light is not visible for other players (just yourself). Turning it off and on again, fixes it.

Just stick this in your joystick lua: {pressed = iCommandPlaneModeCannon, up = iCommandPlaneModeGrid, name = _('Priority A/A GUNS else PCA SELECT'), category = _('3-Pos. Switch Abstractions')}, {pressed = iCommandPlaneModeFI0, up = iCommandPlaneModeGrid, name = _('Priority MAGIC else PCA SELECT'), category = _('3-Pos. Switch Abstractions')},

Stores 2 SELECT :thumbup:

There already is a (active) screenshot thread. Last post 3 days ago. https://forums.eagle.ru/showthread.php?t=160119

Correction on what? Try using letters to explain your problem.

It was posted by Zeus in the Pending Update thead :) .

I believe it might be, MaRQuage. Meaning mark / marking. Does it happen to be a feature to "record" the position you are flying over and allow you entering it as a waypoint Zeus? :D Because that would be awesome. :pilotfly:

It was added a few patches ago. They must have forgotten to put it in the manual. :) *edit* I just remembered there was a lot of complaining and moaning from people about it. Since the (French) M2000C only supports 2 Magics. However, the Greek M2000EG does support 4 (and has different radar and some other stuff). So people started complaining about this being not "a true M2000C" and not wanting it. And others wanting a full M2000EG. In the end. If someone wants to use 4 magics, use 4 magics. If they want a realistic M2000C loadout, use 2 Magics :) So this might be why it is not in the manual. (I believe it is possible in the M2000C, just never used by anyone except Greece, which has the M2000EG)

Different aircraft. Mirage 2000C entered service in 1983. Mirage 2000-5 in 1997.. :) Mirage 2000-5 carries MICA missiles that weigh about 112kg. Super 530s weigh more than twice that.

DECOL requires the FBW test (and trim in neutral, and something else I forgot) CONF indicates the G-Limit needs to be changed. (It depends on your load)

Just check "date modified" when viewing the directory in explorer. The file only get's updated (and so the date updated) when something is changed in the manual. Last month when INS was still to be implemented. It stayed the same for a few DCS updates. Easy enough to look in the directory after a update and see if the field has changed.

You can select in options, to always have a always fully aligned INS. If you don't want full realism and prefer speed.

[ame] [/ame]

It already sorta half works. I did a few runs with it today (after concluding months ago it was still very much a work-in-progress). And if I activate it while flying established and level inside the glideslope. (3 or so miles out). It works just fine. It got me down to ~200ft before having to take over (as expected) every single time. With just having to work the throttle. :thumbup::thumbup:

Inside "Starways Black Sea map 2.4.rar" is a directory named Starways Black Sea map 2.5 :P

No need for gun select on your hotas. Press Magic button on your stick once, it selects magic. Press it again and goes back to gun. Same for Store 2. :thumbup:

Here you go. (It is JSGME ready, just drop and activate). It sits in program files instead of saved because some buttons required a change in lua, so I just made the entire profile there. Just remove your current controls from saved games/dcs.openbeta/config/input/m2000c/joystick (zip them for easy restore if you don't like my changes). One warning, I am using controls from the 1.5.4 version. So you can not use it in combination with the current stable branch. Only on OpenBeta at this moment. So if you run stable (1.5.3), you have to wait until next update :music_whistling: M2000C Warthog Controls.zip

Nomdeplume is correct. You can bind "Stores 2 SELECT" to select 530's if you have them. For magic's use "Magic II SELECT". I've been using it forever and it works just fine. My current hog setup for the mirage is like this: Works great :thumbup:

It was 250 here.. (updating from last weeks OB)

Most 3rd party project planes never do. Mig-21 had a giant update, also, not in the general change logs. Only EagleDynamic stuff (and planes with very minor changes) are in it. As far as hunting for the logs goes. If you enter the Mirage 2000 section on the forum, the very first topic you see is: "Sticky: M-2000C Pending Update Fix List" containing all changelogs for the mirage, ever. You are running the OpenBeta branch of DCS, not the stable one. So changes (and you researching them) are to be expected. And all it takes after a update (or before, a lot of stuff is announced before the update) is check the fix list to see what changed. Just my 2 cents :pilotfly:

Such as these changelogs? Added INS update: bullseye selection. Added INS Alignment update Added INS Auxiliary Gyro Enabled Added INS Damage Added INS Data entry and validation (WiP) Added INS Data entry (WiP) Added INS Flightplan update (WiP TBT) INS Drift Error (WiP) INS Status and Keyboard lights update Combined with a updated INS section in your manual and a full step-by-step howto, for INS alignment on page 90 and data-entry on pages 87-89. What more do you look for? :music_whistling:

Yes. But a lot of servers would want to use the integrity check. (keep for example people in WW2 planes flying with Aim120's and stuff out of their servers..) If you check right now in the server list on the beta. Already about 1/4th of the servers are requiring integrity check. But in my opinion, their should be some sort of distinction in the "integrity check". Such as, "allow graphical mods, don't allow mechanical ones". But I can image that to be virtually impossible to implement. As they already sort of do that (changes in image files are allowed, core lua files are not.. such as starways Shadow lua file. Easiest option to me seems ED white-listing that file in some sort of way. But that's something only ED developers can tell us :)