Martini

When making corrections try making them in 1 axis at a time. I don't have the reference on hand, but I know if you make big, multi-axis inputs you will exceed the available bleed air and lose control/the plane will not respond in a way that matches your inputs. Small inputs, leave the nozzle angle alone once it's in hover range (don't go 80>84>82 to get that last -4 or +4 kts, trim it out and use gentle pitch). That works for me without any issues.

In multiplayer if I set 2 waypoints and display them on the VTB, after I crash, die and get in a new mirage, the waypoints are no longer stored in the INS, but they still show on the VTB (of the new plane). If I then add new waypoints, the VTB doesn't update to show the correct location or number, it still shows the waypoints from the last plane I flew in. The HSI and INS do correctly erase when you get a new plane and do correctly show the location of the new waypoints, it's only the VTB display. Also sometimes I will get scrambled numbers on the Lat/Long page in the new plane and have to enter the new coordinates multiple times before they 'stay'.

Still doesn't work for me...

It looks like the english cockpit was listed as ready for the next update 3 days ago. Haven't gotten on to check, not something I care about at this point anyways since I know all the terminology besides a few random warning lights and knobs I never turn.

+5

Yes, I have the same issue. The only way it's usable for me is to put my nose near where the target should be on the ground then lock, slew works fine then. But it's worthless for searching larger/further areas, and the constant spamming of the unlock button is annoying.

I've been using these y-axis curves (make sure you check the slider box too) which are intended to mimic the shorter pitch down throw on a stick with symmetrical throw and although I am not sure if the actual pitch rate is the same as it is in real life, it definitely seems more responsive than when I had it set to 15 curvature.

I've had this issue as well. Sometimes it works, sometimes it doesn't. I've also had instances where putting the cross on the target's tailpipe at 1-2nm doesn't give me a tone after it failed to slave so I am wondering if it's a problem with the missile or seeker not actually being selected/activated. I will try to reproduce it in isolation and see how to fix it (toggling master arm and pca selection off and on would be my first guess as how to get it working again).

Well this is going to be fun :) Does the plane break easily like in the SU-27 or is it more likely that you'll GLOC first?

I just took a look at the mapping and it's incredibly inefficient. The scripting is cool and all but the actual layout is extremely inefficient and impractical. If you're trying to become proficient with this plane, I'd look elsewhere. Besides one script to drop the fuel tank and one optional one to do a quick start, you can get everything you need on the warthog without any modifiers. There are several fast sequences than you need to execute in combat that with this layout would necessitate you switching between modes, increasing the chance of executing the wrong command and certainly slowing you down.

I was looking through Baltic Dragon's excellent new manual and noticed that it said: In DCS, the ability to exceed the elastic stop is provided by using a button, as flight sim joysticks don’t include a physical stop on the pitch axis. The button used is shared with the AP off feature. Is this correct? I have been able to pull 9g's without holding the AP off feature. I read through some earlier threads and got conflicting information.

Martini Mirage 2000C USA

Could you explain this? I rarely am able to tell them I am out of trim if I am doing BFM or maneuvering hard. If for example I have the stick all the way back in my lap and am rolling left while increasing speed, I will not be able to tell if I am slightly out of trim at that given moment...only when I stop maneuvering hard will I notice that the plane needs to be re-trimmed. Obviously in certain BFM situations I could tell that I am out of trim (if I am level and pull straight back, only using pitch inputs, and the plane starts to roll as I go into the vertical, I can tell that I need to trim LWD or RWD), but most often too many things are changing and the amount of trim needed would change faster than it could be input with the hat.

I still find myself having to trim a bit more with asymmetrical stores once I turn AP off, maybe it's just because the plane is more sensitive to changes in speed/alt/aoa/pitch/roll etc, than with symmetrical stores where you can change the aforementioned parameters a reasonable amount before you need to manually trim or reengage the AP. Just to clarify, the way I worded it earlier made it seem like I had to trim with asymmetrical stores even with the AP engaged, which is impossible to my knowledge in pitch/roll as the trim hat switches to control the AP.

I think a lot of this is semantics at this point. -Blast wants the marginally easier to fly early access fly-by-wire functionality that was either incorrect due to it being easier to program or because Razbam lacked the correct information on the system. -Razbam either got more information and/or had time to implement the current fly-by-wire functionality, which would be 100000% illogical for them to do if the existing fly-by-wire system was accurate - why would they do more work to make the product worse in terms of realism/accuracy? -The people knowledgeable on the topic and the rational interpretation of the mirage stick layout concur that this fly-by-wire/AP/trim system is more accurate than the first implementation -Blast still want the old system because it's a tiny bit easier, despite the fact that this is Digital Combat SIMULATOR that aims to "offer the most authentic and realistic simulation of military aircraft" Am I missing anything here because it seems pretty pointless to continue this discussion unless someone finds some concrete evidence that the updated fly-by-wire system is unrealistic?