Shahriar0

Hi, When flap is lowered, the flap position indicator continues to show flap up when looked at from the rear cockpit looking forward. Similarly when plane is turning, the turn/slip indicator does not show any movement. These are the only two instruments that I have noticed not working correctly when looked at from RIO's point of view. Hope they could be fixed rather quickly. Thanks.

I believe Persian Gulf map can benefit greatly from the addition of Tactical Fighter Base 6 located at Bushehr as well as the Kharq island with it's oil export installations. Currently TFB6 is home to the IRIAF F-14 squadron (used to be in Shiraz but moved to Bushehr during the Iran-Iraq war in the 80s so they would be closer to the Kharq island. The primary mission of Tomcats were to protect Iran's major oil export facilities at Kharq were many aerial encounters happened. With the introduction of Heatblur's F-14A later this year (hopefully), it would be great to have TFB6 and Kharq island added to the PG map. Thanks.

Let me be more specific about the problem I encountered. For all the planes I fly, I assign the necessary "Lights" commands to key combinations (if they don't have preassigned ones) and then bind them to my Hotas profile outside of DCS - being a VR user I want to minimize using mouse and clicking repeatedly on the light dials. For F-14B, they include Exterior Lights Master Switch ON/OFF, Lights Instrument/Console Brightens Up, etc. All those keys were working and present until I upgraded to 2.5.6.47224 after which I noticed that all those assigned keys were deleted and therefore not working. I ended up reassigning them and now they work as before. This had never happened before, either to the F-14 or other planes. Seeing entries in the release notes about keybindings made me suspected a problem introduced by Heatblur.

It appears it is more than that. I have lost all my light key bindings for Pilot and RIO to my Hotas after the 2.5.6.47224 update! Obviously the release note has two entries under F-14B that touch the keybindings. It's possible they are the culprit.

+1

Hi, I thought it would be better to do something more comprehensive. I have some data to share to prove my point. I setup a very simple mission with two airplanes, An Expert AI in the lead flying at 10,000ft and 400Kts, and myself, in an F-14B chase plane (the reason I chose the F-14 was that I could easily read the True Air Speed in the HSA. I also chose the 400Kts, because it was sufficiently above the stall speed of the test planes.) In my test, I flew in close formation with the AI plane, and once it was stable in relative speed, I paused the sim and read the TAS. Below are the numbers (all in Kts): A-10C (400), A-50 (400), AJS37 (300), AV-8B (400), F-14B (430), F-16C (430), F-4E (500), F-5E-3 (350), F-86F (460), F-18C (350), HAWK (450), JF-17 (430), M2000 (490), MIG-21BIS (430), MIG-29A (430). So the implication is obvious, if identical planes are used to set up a formation AI flights, then they all would fly the same speed, and therefore keep the formation; but the AI planes are dissimilar, then they would not keep formation, hence the problem. Also, as you can see, some the speeds are less than the 400Kts. Therefore, a more accurate description of the problem would be, "AI planes fly at different speeds than the one set in the ME." Thanks.

This maybe a function of module rather than ME itself. In one example, I have F4 (Mod), F-5E, F-14B, and MIG-29A AIs flying in a line formation (I am in a chase plane), and with all planes set at 10,000ft/400Kts, I see the F-14 immediately light the afterburner and pulls forward. When I change all the speeds to 500Kts, I see the F-14 first deploys the air brake and then hits the throttle. At 350, they are all over the place. In another saved mission, it is the F-86 that pulls forward from the rest of the formation! I can't seem to find the culprit but the issue is definitely there.

Hi, I have noticed that in my old saved missions where I had a bunch of airplanes flying straight and level together (same altitude/speed) without any issues, now all of a sudden one the planes (and it's always the same plane in that particular mission), it starts to pull ahead and no longer fly at the set speed in the ME! I have double checked all settings and cannot find the reason why this happens. Because this used to work in earlier versions (months ago but can't be more specific), then there must be something happening in the ME. Has anyone noticed this? Thanks.

Hmm, that's what I thought, but the blue mouse cursor was clearly visible in the cockpit of the video I mentioned - which led me to believe there must be a high fidelity cockpit. I suppose not! Thanks.

Hi, I have seen YouTube videos of MIG-29 with clickable cockpit (high fidelity.) I am wondering how I can upgrade my copy, with no mouse, to that version. When I go to DCS page, it says, I already own the module, with no mentioning of high/low fidelity versions anywhere on the site. Thanks.

Is this the same as "Clickable mouse cockpit mode On/Off"? If Yes, then you are correct. That works, so as flashlight illuminating where the blue cross cursor is, as lone as the cursor is showing. The problem, however, is that for the former, I rather not bind yet another key to turn mouse off only to get the proper flashlight behavior, and for the latter, the blue cursor times out (which it should and I like that), but then flashlight remains in one spot until the cursor is moved again. I suppose, what I simply want is the flashlight to illuminate where the headset is looking regardless of mouse being On/Off/Hidden/Showing etc.To me that makes sense. Thanks.

Hmm. I have the F5 and the F14, and in neither of them flashlight moves with VR headset - but my mouse is active since I need to click on buttons, instruments etc. Perhaps this is starting to merge with the thread posted earlier under "VR comms/switch mouse cursor suggestion." I think being able to use the blue cross cursor to click on communication options as well as make the flashlight follow it, would be the way to go. Thanks.

I believe the functionality of flashlight for VR users will greatly improve if illumination followed where the headset is looking at - just as how the cursor behaves which follows the movement of headset. For VR users who try to minimize interaction with "physical" mouse (separate from mouse buttons bound to HOTAS), this will be a great help. We can simply turn the flashlight on and look at where we want to interact with the cockpit, vs constantly moving the mouse around. Would ED consider changing the behavior, or giving us the option of turning on a command and getting this functionality? Thanks.

I previously reported this under the main/general category instead of here. 1) RIO cockpit is missing "Lights Console Brighten Up/Down" keyboard commands. 2) When I assign a key to "Lights Instrument Brighten Up" command, it does not do anything while Pilot cockpit command works just fine. I presume the Down command is not working either, but it did not test it specifically. Thanks.

Hi, I have noticed that: 1) RIO cockpit does not have "Lights Console Brightnes Up/Down" command listed. 2) When I assign a key to "Lights Instrument Brightnes Up", it does not do anything (Pilot cockpit command works.) Appreciate if these two issues can be fixed. Thanks.

What an insensitive remark! FYI, those "static objects with zero functionality" reportedly shot down 159 Iraqi airplanes.

Thanks Nick for commenting. Good feedback. I do realize that I am fairly new to F-14 and still learning it (at a slow pace.) Overtime, I'll get better for sure and experience less flat spins. Meanwhile, I want to make sure I can "practice" recovery just like any other maneuver (used to be a GA pilot and I like to practice procedures and maneuvers, etc.) as well as be able to recover successfully if need be. I am not shy with rudder input (have the pedals) but still managed to induce spin when I was not expecting it - retarding the throttles while in a moderate AOA and slight turn (can't remember the position of my stick). I'll try to recreate the scenario so I know what to avoid now that I realize the choice is not getting into a spin in the first place than recovering from it. Shahriar

Hi, From what I can see, there is no keyboard command to move an engine to idle without cutting it off first, therefore spin recovery for HOTAS with one throttle control is very difficult, and possibly impossible at low altitudes. There is obviously the cutting-off-the-engine option (which returns the throttle to idle position), but trying to crank and restart an engine in flat spin at mid to low altitude in the middle of a dog fight is not practical. I am wondering if there is anything else that could be done that smart folks have already figured out. Perhaps a new keyboard command to just move a throttle to idle would do. Interestingly, after a year of flying in the trusty F-5, I never once had to move a throttle but it seems in F-14 getting into flat spin is a fact of life, hence this question! Thanks, Shahriar

Hi, I accidentally hit the button that uses emergency jettison for the payload and the pylons (bound to my HOTAS) on the ground. It did its job! The question is, is this a bug or feature? Might one think that this should be accomplished via Re-arming window. Thanks, Shahriar

Problem Solved! After Sauerkraut and yourself hinted at a possible interaction with skin, I realized that recently I downloaded a new skin ( https://www.digitalcombatsimulator.com/en/files/3302151/) to correct the color inaccuracy that was evident in the standard IRIAF skin. I ventured into its Description file and noticed two lines that I now realize were responsible for the fuel tank changes. I wish I had looked at the configuration files before posting this thread. All is good again and thanks.

Many thanks Sauerkraut for trying out. It's bizarre that I am the only person who is affected! Still, I prefer that to a wide spread change in DCS. Problem now is that I have no idea what caused it, as I have not done anything to my install base. If/when I figure it out, I'll pass the info for sure. Thanks.

I don't see one. Basically all my previously saved missions load the new skin for the tanks, as well as when I try to create a new mission, or even when I try to re-arm and select fuel tanks on the ground. Only these two new skins load! Gone are the old solid grey ones, it seems. Does anyone else see this? I certainly haven't done anything to DCS but to upgrade to the latest open beta version whenever I'm prompted. Hope this can be fixed soon.

Hi, I just noticed that F-5E had gotten new fuel tanks, replacing the old standard ones. When did this happen, and more importantly why?? In my opinion, they look horrible, and we should go back to the what we used to have before. Thanks.

Sorry, I am not familiar with the DX and TARGET terminologies! I did a quick search and all the results were related to Thrustmaster. I looked in the Logitech software/profile manager and didn't see any references to DX, so not sure how I can test this. BTW, isn't M already assigned for cockpit mirror? If it is, then I rather not to use it. At any case, moving the uncage from X52 profile to DCS worked for me and I'm happy about it. Thanks,.

So there are now two ModelViewer files exist under the bin directory, both are date-stamped September 3, 2018. I have verified that the ModelViewer.exe still does NOT reload model from saved file properly. It must do it from cache and therefore does not show any changes made to the plane texture file. The ModelViewer2.exe, however, does not even run properly. It gives the following error message: "This application failed to start because it could not find or load the Qt platform plugin "windows" in "". Reinstalling the application may fix the problem." It would be nice to receive some sort of notification if there were any changes made to the file so we can check them out. Thanks, Shahriar