Shahriar0

Is there a way to use instrumentation in NAV mode to navigate to a tanker the same way we can navigate to waypoints or airfields? I need this to find tankers at night without using Vector to Tanker via AWACS calls. Thanks.

I have multiple AWACS and tankers in my mission. I am trying to sort them based on my logic. While I have no problem sorting the AWCAS, the tankers refuse to do so! I have created two triggers and activate the appropriate groups per the order I would like to see. The tankers do not sort correctly. I have tried the following to no avail: 1) Changed the order of the triggers (put tanker on top) 2) Combined the two triggers into one 3) Changed the ONCE trigger type to ON MISSION START Basically I tried all variations I could think of but could not get tankers to sort. Am I am doing something wrong or is this a defect in Mission Editor? Any tip on resolving this is welcomed. Thanks,

I was just flying over Qeshm island in the Persian Gulf map and decided to land there. My ATC contacts for inbound and subsequent request landing from tower were answered with Krasnodar in the Caucasus! Also once landed, the runway edge lines as well some parked AI planes in the parking area appeared to be hovering a foot off the ground. Not sure if other fields in the vicinity are affected or not, but it's likely. Hope it gets fixed soon. Version is 2.8.1.34667.2 Thanks.

I suppose. I have no problem jumping to back seat and doing stuff.

I was actually in MP.

Workaround is to jump to back seat and toggle pilot body there. The front seat pilot body will then disappear. On a different note, I jumped on a multiplayer server, launched a Phoenix C variant in TWS-Auto mode, which was defeated by maneuvering plane. Once I activated ACM and locked via PAL and pressed trigger to launch, the computer rebooted! I have had this problem before and only happens with this module specifically with Phoenix. It happens frequently enough that it is always in the back of my mind when launching that missile type. No crash files are ever captured. Edit: Not all the reboots have happened in ACM with PAL mode. Routine TWS launches also account.

This is exactly what I was looking for. Many many thanks!

Any comment on the above request HB?

I would like to see two keybindings for pilot to increase and decrease radar range for Jester AI. Currently there are fixed bindings for this; "Radar Range - 25/50/100/200/400". Instead of using 5 buttons on Hotas to map all the ranges, we can use only two buttons instead. Right now due to lack of available buttons I'm only mapping the 50 and 100 ones to my Hotas. I believe there are other modules that already support this. Thanks!

I would like to provide an update to the original problem I ran into, which was airplanes drifting to right in DCS. It has been solved! While continuing to research issues with X52, I ran into a post where someone was experiencing a particular problem with his rudder action. Rudder was either in full deflection to the left or full deflection to the right! Any slight twist in stick would send airplane rudder all the way to its full motion. Solution was to delete X52 calibration entries from Windows registry! Even though my problem seemed different, and the fact that I experienced no drifting to right (in the form of slight bank action) in MSFS 2020, I decided to give it a try. To my amazement, it worked! Now, the plane flies straight, as it should. Just in case, others may experience weird issues with their X52 Hotas and read this thread in the future, I would like to offer the following solution: - Back up your Windows Registry. - Go to HKEY_CURRENT_USER -> System -> CurrentControlSet -> Control -> Media Properties -> Private Properties -> Direct Input - Delete any entries inside the Direct Input folder that begins VID_06A3. - Reboot your computer. Even though my problem has been solved, I think knowing how to set trim presets in DCS would be beneficial to some. So I hope ED would still consider providing an answer to it. Thanks.

This question is still standing. ED, please provide a comment. I am sure someone over there readily knows the answer on how to enable presets for trims either per-module or for the entire program.

ED, could you please make a comment on this?

No, I'm not, but thanks for the tip. I'll see what I can find out. Meanwhile, ED's teaser of 2022, has revived my dream of having a full-fidelity F-4 module in my hanger - which will of course solve all my problems Thanks.

Bump.

Tried 2.7.3.8494 (30.06.2021) with the same result - with a minor difference that AI launched its Fox2 at 1.5NM. This beats me. I'm sure I have done BVR with AI launching AIM-120s at me in the past. I just don't know the details to nail it down. Still, my question stands; why doesn't AI launch AIM-120/7s??

Attached is my simple test mission. The mission starts with a Blue F/A-18 AI with Fox1/2/3 at 50NM. Initially the RWR in MiG-29 shows the AI radar on, but after a little while the radar turns off, and hence it never launches any of the Fox1/3. When it reaches about 3NM, AI fires its Fox 2. I went back to the 2.7.6.13436 release (29.09.2021) but it behaved the same! Now I am trying an earlier image, but the download speed is very slow. It might take some time to reach a conclusion. Meanwhile, I am hoping someone could explain this behavior if indeed is the correct implementation. Thanks. AI Won't Engage.miz

That's about right. For me, they engage around 25+ miles, but at least they do. When it comes to other AI planes, there is no engagement and no missile launches whatsoever! My plan is to go back a few releases and compare behavior (while keeping my test missions exactly the same.) I am fairly certain I will find a release in which the AI would engage, so I can report back with concrete evidence.

Hi, Has anyone noticed a change in the behavior of AI in terms of engaging in air combat in the recent releases? I have these saved SP missions that I use to practice BVR from time to time, and for the past several years they have been working as expected; AI planes launch their missiles as they get in range. Now, I have noticed that, the RED side, has signed a non-aggression pact and they do not launch at all! In fact, if I don't launch myself, they simply merge. The missions are super simple. There is a Blue and a Red side, with the task set to CAP (I have tried others such as Intercept with the same result) and the skill set is Ace. Most of the planes I practice against carry AIM-120C - if that makes a difference (for F-14 AI, it actually does. I have noticed that lately when they carry AIM-54A-Mark47, they do not launch at all. When I change the missile type to Mark 60, they do.) Beside ED tweaking the behavior to correct this, how can I make the Red side engage in BVR for now? Thanks.

Can I expect some sort of solution to this, or am I at a dead-end? Thanks.

Thanks for commenting. I did run into this suggestion when I was researching this topic and, as you said, it's not the optimal solution for various planes. Meanwhile, my problem has taken a bizarre turn which might steer it in a completely different direction! For the sake of thoroughness and ruling out that this is indeed a problem with the HOTAS and not the flight simulator, I did a whole of testing in two different programs, MSFS 2020 and X-Plane using mostly planes with jet engines (to eliminate the problem of propellers and torque and drift to left/right.) To my absolute surprise, I do NOT see any drift in any of the mentioned programs in several different planes that I tested, to the point that, I would like to say this issue of drifting is now limited to DCS and recent product releases of X52! This is a headscratcher to say the least. I know from the perspective of Windows, my new X52 was treated as a new hardware device and I had to install my profiles both for X-52 and inside DCS. So there is a chance, there is something that triggers this problem, but I do not know what. I plug in my old X52, and all is good. I fly handsfree and there is no drift. I plug in my new X52 and the drift is immediate and very pronounced. Go to another simulator and there is no issue! I very much like ED developers to chime in to shed some light on this and perhaps offer a solution. Still, my question is valid, how can we preset trims in DCS. This is something I used to do in X-plane myself (there is a line in aircraft.cfg for each plane that allows exactly that.) So we are not really asking ED to divulge something out of bounds for users.

Hi, I would like to know how I can define presets for various trims (aileron specifically) in DCS that would apply either to all planes, or on a per-plane basis. This question has come about as a result of a peculiar problem I have with a certain HOTAS, the Logitech X52. Apparently newer products have a tendency to drift to right! This became apparent when a couple of years ago, a DCS buddy of mine bought his new X52 and noticed this right-drifting tendency. He went through exchanging several units before realizing all displayed the same behavior/problem. Meanwhile, my own X52 that was bought in the 2000s shows no such problem. It flies straight when there is no input from stick. Yesterday when I received my new unit (as backup), I immediately saw the same exact characteristic. Apart from contacting Logitech (which was done a couple of years ago by my friend, with the ultimate result of the ticket remaining unsolved and all emails unanswered!!), my solution is use left aileron trim to compensate for this drift. This works, but obviously, I don't want to spend anything between 5-15 seconds of every single flight I am going to conduct to trim for a straight flight. Please note that, trimming takes a bit of time. After an input, you need to observe the result and see if trim was enough or was overdone, etc. Best solution in my opinion is to use preset for aileron and find a value that compensates for the right drift for this particular HOTAS. I have searched the forum and tried all the various suggestions to no avail. That includes the most obvious one to add aileronTrimTab = <value> to various files such as FMOptions.lua file. Unfortunately none has worked. What I need to know is the exact syntax of the command, if different, and the location of file (per DCS or per-plane) to include. Also I would like to rule out other things that do contribute to a drift, such as rudder not being dead-center, uneven fuel, unbalanced plane balance due to dropped ordnance, impact of defined dead zones, etc. To add that X52 has no calibration of its own. It re-centers itself after every boot. When I use my old X52, I can take any plane and fly straight with no problem. I disconnect and put the brand new X52 and in every plane it shows the exact right drift by the same amount (it 30 seconds, the plane is banking a good 10 degrees, and the bank continues as time goes on unless corrected.) Interestingly the Axis Viewer in F-14 does show a very minute amount of tilt to the right (the four areas of the trim diamond divided by the axis are not the exact same size.) This is harder to detect in Axis Viewer for different planes due to the size and shape of trim symbol. Thanks!

I'm using KC-135 tanker, and Phantom with a receptacle behind cockpit similar to F-16 (which I have refueled successfully with the same tanker) should have worked, right? Also, the VSN_F4E.lua file has the REFUELABLE attribute, although the location of the receptacle is all 0s (which would be my next question as how to find the correct coordinate.) Thanks.

Hi, I am having trouble contacting a tanker with VSN F-4E mod. I just downloaded two VSN modules; the F-4E and F-22. They work and look great. However, in the same mission, when I choose my client as F-22, I can contact a tanker to refuel, but in the Phantom, the tanker does not return the call to rejoin. Dead silence! I have looked at everything but cannot seem to find the culprit. If I change the Phantom to say, FC3 F-15C, I can talk to the tanker, no problem. I am running the latest OpenBeta as of today and modules are the latest versions. Any ideas? Thanks.

When radar is turned off or put on standby manually and Jester for no reason whatsoever turns it back on, I call it broken.

Correct, but I need Jester for other things and would rather not disable/re-enable it. Instead, I rather see HB fix the logic of Jester where broken, or seems unnecessary, if possible.