AJaromir

Good day. Lot of aircrafts and helicopter in DCS have a lot of special options settings. Just like rudder trim, left/right/both HMD render eye, afetrburner detent, e.t.c..... My problem is that I don't know which setting is the most realistic. It is not written in the special options tab. Woul'd be possible to make some marks at those most realistic options, please? Also, because it is quite annoying to ask developers one by one, woul'd you give them my request if you agree with my opinion, please? Thank You a lot.

And isn't possible to save this to "%userprofile%\saved games\dcs\config" folder? Just like you want to make fps limit, then you create in the notepad++ the "autoexec.cfg" file there and write in it: "options.graphics.maxfps = 120"

Thank you, Baur. This solved all issues. :)

Thank you! I will check that tomorrow.

Just one note. About 2-3 months ago there was no problem with that. Does anyone have the old firmware versions to check that, please?

The problem persist with 20180913_upd3

Here is the video: I use the most recent firmware. In the video I was not changing the grip. I was only re-saving the already saved profile.

Hi! I use 2 grips. T-50 and Warthog. Every time I change the grip from T-50 to Warthog and profile, the Stick ID is changed so. This woul'd not be the problem, but when I change grip back to T-50 and load T-50 profile, the ID is not same like it was before the first change. So every time I change grip, I have to find what is new joystick ID and rename the *.diff.lua file in %userprofile%\saved games\DCS.openbeta\config\input\desired aircraft\joystick\ And I am not sure if the ID changes with the calibration too. Edit: I will take a video to better understand what's going on. P.S. Thank you for any help. Because this problem is really annoying :(

This problem is still not fixed in 2.5.2.20601 Update 9.

Try to delete the "metashaders" and "fxo" folders in "%userprofile%\saved games\dcs"

Same problem here.

Not a a bug. The lights are just only on lower blade tips.

Looks like you are right. The course seting is not needed for ILS. But for VOR/TACAN is needed. There is difference between heading and course. The VOR/TACAN are independent on INS because those are fixed ground point and providing information about azimuth and distance between the VOR/TACAN and aircraft. By course knob you just set the azimuth between VOR and yourself which you want to hold or check, not the heading. Also this is the difference between the NDB and VOR/TACAN. NDB is just provides the direction to beacon but not the azimuth/distance. VOR/TACAN will tell you your geographic coordinates without need to have compass.

Actually every aircraft that I know needs the course input to work properly with the VOR/TACAN/ILS

I don't uderstand then. Because this is how it in DCS works for years. You just set the runway course into HSI and the flight director bars on ADI are compensating the deviation caused by the crosswind. Just like I've wrote. That makes landings much easier. And that is how flight director should work.

Well IMHO, there is difference between the HSI course deviation bars and ADI flight director bars. The deviation bars works only with the ILS signal. But IMO the flight director can not operate properly without knowing the runway direction. Because when there is the crosswind and the system does not know the runway course, it will navigate you with the deviation caused by crosswind. But when the system knows the runway course, it can compensate this deviation caused by wind.

Looks like the LOD error

This also applies to aircrafts. Screenshot taken in 2.5.1

Same here. Tried now in 2.5.1 ILS not working. Also the steering bars not working 100% perfectly with the TACAN. The steering bars navigates me with the deviation from desired course. I will check some other aircrafts like F-15 if the ILS works correctly. In Russian aircrafts like SU-25T or SU-27 it works properly. Edit: found that in some MP servers the ILS works properly.

Thank you all for answer.

Good day. In the manual, page 239 is written: I don't understand this sentense. Does it mean: 1) I have to turn on NAV mode at least 2 minutes before take off? 2) I have to take off in 2 minutes after the turning on the NAV mode? Thank you for answer.

Just uninstall release and download the new 2.5 release installer. It will not download anything. The updater is smart enough to copy data from already installed OpenBeta root folder.

Falcon, I can not agree but not at all. (Just I agree but not at all) I am "cooperating" with the mission Creator for not mentioned server which is in my eyes the best training servers and running on very powerfull rig. There is not so much targets but there are scripts that they can respawm the targets once they are destroyed or you can spawm your own via special radio menu. Also this respawming causes short freezes. And I guess the units are not loaded in memory until they are "physically" on the battlefield. Also I wonder to know why taking the screenshot will sometimes freeze the game for all players.

Just some modules can have tons of polygons or really superhigh textures resolution. E.G. once the Mig-21 was released, it had really damn a lot polygons which were heavily reduced because they caused the heavy HW load.

And how about to make something like the "slowed" or "delayed" loading? For Imagination: