Joe1978

I don't know if it has been reported; the radar screen was moving inside the cockpit, and the illumination of the sight was also moving at the same time/direction. nullI'll try to upload a track tonight.

Thanks Stick,I was trying to keep the previous versions (2.5.7.01 y 2.9.1.01) because the Mirage IIIs look like more older models. What I've done is install the latest version (v2.9.16.201 +SkinPack ) and tweak the Luas a bit so they now can load AIM9 B,JULI,L

Question (stupid probably) Where should I add those files within the mod? I installed the folders—Mirage5, etc... in the liveries, but DCS only shows MirageIII files. C:\Users\Saved Games\DCS.openbeta\Mods\aircraft\Mirage III\Liveries. null

I'm tempted to buy it right away, but I'm also worried about how long it'll be in EA and if the developers will can fix any problems quickly.

I'd pay for a Mig21 upgrade right now, but I can see both sides of the coin here: Having already four aircraft without developer support (RB), and with Mag being so uncommunicative (and not very proactive resolving some issues), questioning the purchase of one of its modules (including the F4U) is like a leap of faith... although that's what DCS is all about. My advice: enjoy the MiG-21 as it is. We have great maps right now. It can do almost everything it was designed to do.

Thanks. Yesterday it happened to me several times... plugging and unplugging seemed to solve the problem but after loading a new mission, it happened again.

After the latest update, I'm having quite a few issues with my AVA base. Has anyone else had problems? It seems like DCS detects it (it appears in the menu to add functions in DCS), but it doesn't receive any input. I keep plugging and unplugging the hotas until I can finally move it.

Thanks NineLine, we've been dealing with this issue for several years (and the developer has been looking the other way). If you look around here, you'll see several threads related to this issue. Tonight I'll try to record a track with the Supercarrier and Tomcat.

For me, the problem with radar in VR is that the clutter is always displayed in this way and in a static way and with this same image... if you rotate, for example, the image will remain the same.

No, in low altitude mode the search antenna is disconnected and will not display an image on the screen but the distance markers will be on (red). Second, the radar mode switch has always been backwards. It's a bug that has never been fixed (switch in position 2 is low altitude mode instead of 1).

In VR low altitude mode works

Ummm I just test it on 2D (I haven't used it for years) I have found two types of returns... The first screenshot is what I'm used to seeing in VR (circular blobs). The second is what I found in 2D (white block) For both tests, I used the dynamic ground return option. I agree with you, there's definitely something there. Unfortunately, even if RB were there, I highly doubt they'd support us. Edit: Low altitude mode doesn't seem to work in 2d... I need to do some tests agaim

For me, it makes sense that below 2500 meters the radar is blind... At least it brings a bit of "realism" to a module that RB never pampered.

This is what I was trying to explain before (I only use VR). Below 2,500 meters, you'll have that effect that "simulates" the clutter/noise The noise/return is simulated with that "static" image that you show. Above that altitude, the radar will return to normal operation. This has been around for many moons. Edit: Forget about the messy/returning like in more modern modules where the image is dynamic. The MiG-19's radar was simulated very simply.

It works that way even in low altitude mode/mode 1. Remember that the MiG-19's radar was never fully modeled by RB. Clutter can only be eliminated by flying at higher altitudes. Close to the ground, it's blind. If you fly low and place an aircraft 2 or 3 miles in front of you, you'll see how the radar detects it despite the clutter. In terms of simplicity, it works "similarly" to how a primitive radar should.