Shahriar0

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

Not that it made any sense to me whatsoever, but out of desperation, I went ahead and deleted the Missile Uncage button from my X-52 profile, and defined it under the Controls inside DCS. It worked!! I don't understand why but it did. Obviously I see this as a workaround and not a good solution as I prefer to have all my keys defined in 'one' place, be it X-52 utility or inside DCS. For me, X-52 provides far more flexibility compare to the DCS. For example, I can make a slider or a rotary knob function as a band and define keys/actions in different percentages of the band as I wish. At any case, I have a solution, and now I can finally see whether all the debates about using or dissing missile uncage has any merit to it or not! Thanks.

Inside the X52 utility, I can test the keys and see that HOSTAS is sending the right commands. When press and holding RShift-M, those keys keep getting sent and then when I press the RAlt-Space, that's what is sent repeatedly. Not sure, how DCS is interpreting them inside the game. Under the control. I don't have anything defined or changed. I played with changing the Button to Macro and Advanced Buttons for X52, but none worked. I have to say two things have surprised me so far, 1) F-5E developers did not pick a key for Missile Uncage that would not have this conflict to begin with, 2) It seems everyone else is an expert have already solved this on their HOTAS and I am the only person who is struggling to get this done!

Interesting. I use Saitek X-52's own utility to program all functionality outside of DCS. I'm not sure how I can avoid this conflict. Need to dig deeper into that utility, I suppose. Appreciate your comment.

Hi, I have the most basic question about the operation of Missile Uncage. The manual states that: "Continue the target approach until seeker lock-on audio tone is heard. Push and hold MISSILE UNCAGE switch |RShift + M| after seeker lock-on to facilitate maneuvering to advantageous attack position. After the position is taken, push BOMB-ROCKET button to initiate launch |RAlt + Space|." With the keywords being Push and Hold, how come missile does not fire when Missile Uncage key (bound successfully to my Hotas and visually operating) is selected and held while missile fire key is simultaneity pushed!? Missile only fires when I release the Missile Uncage button - which obviously means the seeker-head will only straight forward and in a lead pursuit will lose lock. I also know Missile Uncage actually works, because once I move the target off the reticle while holding the button, the lock is maintained in the time specified in the manual. My problem seems to be how to fire missile! Finally, I have tried using keyboard shortcuts and result is the same. Thanks, Shahriar

Percentage wise, it may not be that large TODAY. but in time, after a number of years perhaps 10 more modules and two hundred+ liveries, it will be! I'm sure of that. I suggest planning on doing something today so that when we get to that point in the future, we'll have an option to deal with the situation then. Aside from space consideration. it's the idea that you're being forced-fed when you actually don't need food albeit it's tasty! It's respecting customer in my opinion. Thanks, Shahriar

Thanks for commenting. I guess I am not convinced that having an array of real and fictional liveries are essential to operation of DCS. What I am saying is that a new module should come with absolute necessary and bare-bone liveries. Then, it would be up to the user to download whatever "extra" they want to install and enjoy. Everyone (including DCS) will be exerting enough control over their installation to keep them happy - and functional at the same time. If I was up to me, I would make it even user-selectable whether to install a new module or not. Let's face it, majority of us are only using a few modules. Myself, I am happy with a single F-5E module and the upcoming F-14A. Done! Thanks,

Hi, I would like to know why deleted modules/liveries (deleted for whatever reason, be it space consideration, or that the user has something personal against a specific module/livery!!) are re-installed automatically? Why is there a need for anyone who is running DCS to have an exact list of official modules/liveries? For Multiplayer, I understand the logic, but for me personally, to fly in single mode without using missions that require the unwanted modules/liveries, I should be able to do so. The DCS liveries is simply growing out of control. For every new module (most are unwanted), many megabytes of precious space is getting wasted, and it seems users are not allowed to get rid of them!! Please comment. Thanks, Shahriar