Akiazusa

Nice to know that

Sorry,I got it wrong. I must have a bad memory.

IIRC any ranges above 80nm of VTB is for navigation purpose,mainly to show BUT waypoints,the radar is still working in the background,but no radar contact will be shown

There are a lot of factors that will vary the radar detection range a lot. In ideal condition the Mirage can pick up and lock fighter size target like su27 at 65+nm without problem(see screenshot below) You will have a greater chance to pick up a head on high speed target at far range in the Mirage with default radar settings,but if the target is maneuvering around,you will have to change radar settings (PFR,A mode,BAR,Azimuth,Doppler Rejet,etc) to match the target condition.

F18 longitudinal control law?

Did you apply the normal wheel brake while setting the parking brake? On Apache you need to first apply wheel brake to let hyd pressure build and then set the parking brake to lock the pressure in. If you missed the first step,the parking brake handle may come out but no hyd pressure is locked in the pipe. Also if you apply normal wheel brake after setting the parking brake,the parking brake will release automatically.

You need to cycle the flight controls several times before doing the FBW test now I think,especially in cold weather.

In the game manual I believe,it has been updated,there is a change list of the manual at the page 18 and 19,check that so you won't need to read the whole manual again.

I never though things like radar emission channel would ever be implemented in DCS,but Razbam just did it.Plus the new RWR,ECM and DTC,Really surprised by this update. Seems everyone is enjoying the Apache right now and it's really quiet right here.

Personally for me,I am flying the Mirage for now while waiting for the official JF-17 manual. The Mirage is relative old and lacks things like FOX3,GPS and TGP,which will force you to keep the lock during BVR combat,constantly update your INS position and do IP bombings.But you will also gain more experience by doing these,which will help you a lot when you finally switch to the JF-17. Besides the Mirage is a joy to fly with some very unique French features that you will never get in other dcs aircraft. The realism of both aircraft should not be a problem as Razbam is working with French Air Force and Deka has some sort of relationship with the aircraft manufacturer,but the lack of an official manual of JF is really a pain when you want to know some small detail of the aircraft.

The difficult part is that they need to balance how deep the systems will be described in their public manual，so they won't be taken down by the government. Personally I hope we can get a manual like "that f-16 sim one" or the dcs manuals for the Tomcat and the Mirage.

Hi IIRC it works. You can only control radar gain in VIS mode but not DEC mode,in VIS mode it helps you clear out the return pictures and find things easier. In DEC mode it won't do anything because in terrain avoidance mode all you want to know is where ground level is higher and where is lower，gaining down those red returns is not good for pilot health But instead you can use radar elevation control in DEC mode to choose a safety altitude above which the return will be printed in red the radar gain control also works when PFR switch is in ENT or BFR and you are in a bar search，the VTB display needs to be 40nm or lower for radar raw returns to be displayed and you can adjust the returns just like in VIS mode

Thanks for the explanation. And really nice to hear what's coming in the future.You guys are the best.

I bought the Mirage when it was out a long time ago and re-picked her up and started flying it recently.I am really impressed by the amount of details and works the DEVs have put in it. Now its my favorite jet in DCS World. I read the change log from last update there is a "Gong when crossing selected altitude +1000ft and -300ft even with AP off " in it. I'm curious about it because I thought I can use this it to notify me when in some situation like passing Transition Altitude. But I find the Gong seems only went out when crossing selected altitude in a descent but not in a climb. The gong will go off twice ,one for descending passing selected ALT + 1000ft and one for descending passing selected ALT -300ft. What's the exact logic to trigger it? Another one I noticed is when I doing a start following the manual.When I doing the TEST for caution lights,the red light in the landing gear handle will flash when I selected test1 but won't flash when I selected test2. Just curious if this was intended. The last one is about VTB symbology in Arrière – Rear mode,The Route désirée d’arrivée symbology is not displayed in Arrière – Rear mode in the game.It might be pretty useful for navigation if it were displayed. I don't have a manual of real Mirage about this and it's just a question.If it is not displayed in the real Mirage then its prefect for it now in the game. Thanks for answering in advance.

Thanks for the information. Amazing work.

Hello,after the most recent update it seems that the IDN heading flags is stuck and won't go off no matter what. You can jump in a hot started aircraft or a flying aircraft in the game to verify this. Anyway,it's not a big issue and thanks for the nice update. edit:I find it only happens to the French version cockpt,but if I switch to English cockpit the problem is inverted,the flag will stuck at off position instead.

IIRC,the original DCS A-10C is a high-fidelity Desk Top Simulation of the Suite 3 A-10C developed for the U.S. Air National Guard and for pilot training purpose. Then re-programed into a game and first got EA release in 2010.However the COMM page is not part of the Suit 3 A-10C and was added to the real aircraft on 1 May ,2009. Only hafe year before our game version got first published.The TM manual on the internet was published in 2012,one year after the full release of our game version. Their is a change list of what was added to the real aircraft at what time at the very beginning of the TM.By the time our game version Suite 3 a-10c got a full release,they already started upgrading Suite 6 Software and Hardware on the real aircraft. So there wasn't anything wrong for our A-10C without the COMM page. And it is already a feature that is going to be added into the A-10C II before it's done. Just be patient and don't push the dev too much. If they rush their work and get something implemented wrong or buggy,people will complain and ED will have to waste time and resource to re implement them again.It will be a double lose. Also I don't believe real pilot will learn their plane by reading through the thousands pages TM/FCOM page by page,word by word.It's nothing wrong to read ED's manual as long as they write things right.

Sorry it seems that I actually reported 2 bugs in the same post. But is the ATC display logic on the HUD correct? In the sim it will only flash when ATC is disengaged,but not when an unsuccessful engagement of ATC is attempted. If you try to engage ATC without a suitable condition (ie :try to engage ATC with 2 throttle levers at different positions,or try to engage ATC with FECS channel 2 or 4 circuit breaker pulled),the ATC engagement will not be successful,but the ATC display on the HUD will not show up and flash in these conditions.

With MC1 off ,the DDI SA option should not be available on DDI TAC MENU,but it is still there, you can enter SA page in the sim but after that,you can't leave that page by pressing "MENU" DDI pushbutton again, unless you turn MC1 back online. DDI SA.trk

In the sim，after landing gear door have been blown away , the gear doors are gone and the actuators of them stay in the open position. So I think that if you overspeed the gear doors and then retract the gears，the landing gear warning lights on the gear handle should stay on due to lack of gear door close signal,and thus trigger the landing gear aural tone after 15 seconds,which is also a good way to tell people the gear doors have been damaged without switching to outside view. But right now the landing gear warning lights won't lit with up and locked gears and missing gear doors. Landing Gear Warning Lights.trk

Track uploaded,sorry for missing it. FPAS climb.trk

Track uploaded,sorry for missing it. At start of the track I turned on the ATC, and changed the flap switch to different positions,but the ATC didn't disengage. Then i pulled out the FECS channel 2 circuit breaker,which will prevent ATC from going active,and then I used throttle button to turn the ATC on,which in theory should trigger a 10 second flashing ATC symbol on the HUD,but it didn't happen. ATC logic.trk

As title says..... from NATOPS manual: If I understand it correctly,the Climb Pushbutton on the FPAS page WILL be removed from FPAS page when master mode is not in NAV,but will NOT be removed when HUD reject switch is out of normal position. But now in our sim it works inverted,it is not removed when master mode is not in NAV,but do be removed when HUD rejection is selected. It's just a small detail actually.....just write it out in case of I forget it one day

3 years has passed,this problem is still there. Has any DEV noticed this And if I understand it correctly,besides the current range and endurance values being replaced by "Mach" and "LIM", some others values on the FPAS page should Xd out when flying above M0.9.(such as home waypoint number)

I'm not sure if they are bugs or some avionics differences IRL,but right now they seems work differently from the NATOPS manual I have. In the manual about ATC ,it says: "If either mode does not engage when selected, or automatically disengages after engagement, the ATC display flashes for 10 seconds and is then removed from the HUD." But in the sim it will only flash on ATC disengagement, the "mode does not engage when selected" part is not true in the sim. And also in the manual about ATC:"When either mode is engaged, changing the FLAP switch between AUTO and HALF or FULL automatically disengages the system." But it seems like the automatically disengagement in the sim is based on actual flap position instead of flap switch position. So the changing flap disengagement only happens when you fly slow but will not work when you fly fast. They are not big issues anyway,hope somebody can take a look when not busy.thanks.