PiedDroit

I think people got it now... And FYI, when a dev talks about "definition", he's not talking about dictionary definition, he's talking about a piece of code that will magically do something. In that case, define a light that lights up stuff. Wrong definition means using the wrong code piece. Call it a bug.

Here: http://forums.eagle.ru/showpost.php?p=2685531&postcount=12

You need to set the coordinates you want for the RIGHT_MFCD view port (which is just a name anyway). In your monitor lua file, add this for example: RIGHT_MFCD = { x = screen.width/3; y = 0; width = 400; height = 400; } P.S.: Either edit the lua file under \DCS World\Config\MonitorSetup or create a new one (copy of the default one), then change the file name and the name inside, in \Saved Games\DCS\Config\MonitorSetup @Zeus67: try_find_assigned_viewport can use an alternate name, for example: try_find_assigned_viewport("VTB","RIGHT_MFCD"); will search for "VTB" view port, if it doesn't find it will use RIGHT_MFCD viewport. This allows even more customization, while keeping it generic for users who only define RIGHT_MFCD.

I don't think I know what VTR is :huh: If VTH (HUD) -> switch is hidden behind the lower left corner of the HUD console, click only once or you will go in test mode. If VTB (HDD) -> switch is on the lower right, labeled M/A

I was just, kind of... confirming this. Yes. I knew it. Of course. Obviously.

I don't know if it's related, but I had crashed after missile hit too, once, it looked like the aircraft did a quick flip, just like when you use the FBW gain switch. Maybe this is related to that crash people had when using this switch then pulling so hard the wings got ripped.

Cool thanks! Regarding that lock problem, I didn't have it again so far, in the release (100% sure I had it in 1.5.2, not so sure for 1.5.3). Maybe it's was only me hitting the lock button too much, will keep an eye open.

I had this too in OB 1.5.3. I will try to make a track out of it if it happens again, in the release. Also, the radar unlocks when pressing lock again while already locked in PIC, which doesn't help. I don't know how it is in the real aircraft, but a lock button should never behave as unlock IMO :music_whistling:

Oui ;)

Also, as per manual, most instruments should indicate mag heading, except HSI in cv mode. HUD should always show mag I think. In Caucasus we should get True heading = Mag heading + 6°

Fingers crossed ;) What is MAWS' detection range? I don't know if it can detect a long distance (e.g. BVR) missile launch.

I'm French native so OK here ;) I actually added the french name to my post right after you quote it. No worries, you could know only if you followed the dev threads. I was not 100% sure we have it but it seems the Mirage version of DCS had it, the devs told they would implement it. Good stuff! Regarding RWR, I'm not very familiar with the Mirage's and it doesn't seem to detect the launch of SARH. I don't know if it's intentional or not, and there is nothing in tje manual yet about it.

Nope on your nope. It's called D2M (Détecteur Depart Missile)

They already know, they even warned us that it would be like that.

If the year is not written anywhere, we can pretend what we want ;)

Super, thanks! I asked about this on the OR thread a while ago without an answer, now the answer is here :D

What I. mean is that depending on which volume you want to scan (providing you scan same altitude), the angles will be different. The farther you want to scan, the lower you aim, because of earth curvature. Without knowing how the radar is aiming, it's not possible to make computations like this.

You forget to take the earth curve in account into your computations I think. edit: also, we don't know where the radar is pointing exactly, in relationship with the scan max distance.

See my post, close enough

Sneaky button 30... :D

You can still do CCRP and dive bombing. CCRP doesn't mean "level", it only means that you need to designate your target before release. What you can do is dive, designate your target during the dive.

:thumbup: Also, fixed inventory is a fixed point in time. Ideally, we would load "inventory configurations" for each country (ex "UK 1980" or "Generic West 1960", "Low tier 2001"). As of now, the only thing that can be done is study the technologies then tailor the available equipment according to the scenario needs.

I don't agree here, there shouldn't be any per-country limitation. Otherwise it closes the door to a lot of scenarios. Even without considering the scenarios, if I'm in Canada and I fly a Mirage-2000C, then I want to be able to fly a Canadian Mirage. Simple. P. S.: In other words, aircraft/weapons availability and skins is up to the mission designer. The game engine should only have a sandbox role.

I'd suggest a DCS repair, none of this seem normal. I don't use the idle detent at all, here's how I start the engine (I'm not going into details): throttle 0, pumps and vent ON, push ignition. At 11% RPM, push throttle a bit then go back to throttle 0. Did you try that sequence without using the throttle axis at all (i.e. using Num keys)?

To imagine what it would look like, just sit at a confortable distance from your screen, with a nice AGM-65H wallpaper for better effect (use this video for example, pause it anywhere with a TGP view: ). Let's say 1.5 metre (5 feet) from the screen. Then, form a circle with your hands and hold it in front of you (or cut a 10cm diameter circle into a sheet of paper for better effect). Now, look at your computer screen through this circle (the screen should fill the circle). This is how you would see a collimated screen. Move your head left and right while the circle is fixed in space and see how the image behaves, it's much more confortable than a a tiny image that would have the size of the circle (even if your eyes need to be aligned correctly to see the full image).