whitehot

Don't know if it's old or new, but in the mission editor the helis (KA50, Mi8, UH1 and SA342) can't start from any ship except carriers. In addition, textures on the "Moskva" cruiser are missing

After some initial adjustement I i've learnt to control this helicopter as good as with the others, i can't say i'm dissatisfied with the result. What has always bothered me, it's a sensation of "low res" of the flight model, like the tables from which is formed contain a small amount of values. this translates imo in unrealistic transition phases. Another impression i've got after flying it for some hours, is that the collective variation effects on pitch/roll/yaw are way too linear and inconsistent. Under this respect, helis like the Hip, or especially the Huey, have a very recognizable reaction to, for ex., an abrupt increase in torque. This fm instead, seems almost to be "missing" that part. Try putting the heli at a slight roll angle, then quickly (or slowly) increase collective. I mean, what happens doesn't seem realistic to me, it remembers me of the behavior of old DOS flightsims. I'm not saying that the true gazelle can't be like this at all, but the impression that the fm is missing some data in that department is heavy.

is it possible? perhaps through tweaking the loadout inis?

I've been trying to remap my controls after a reinstall, and i am now unable to save "modifiers" keys, in particular those of the Saitek X52 Pro. The keys are saved when first assigning them in the controls section of the options, yet they are not retained after exiting DCS and starting it again. At that stage, all the commands which were assigned with a modifier are listed in red background in the options and they do not work. Already tried: Repairing DCSW several times. Completely delete the input folders and let the program rebuild them. The hotas is connected always to the same USB port. This issue was not present before reinstalling the sim.

You gave me the idea that solved my problem. I've had the presumption of backing up the content under the "Saved games" directory in Windows 7, and then apply it to the Windows 10 install so to keep my settings and things. Of course it was a purely delusive thought, that made me think that it could work. Deleting all the content under "saved games" and let DCS build a new one made it work. Now, control remapping it is. thanks for your answers.

Last week I updated from W7 to W10 64 pro. After installing all the relevant drivers and prerequisites, went to update and repair the existing installation of DCSW, that was sitting on my SSD. I've had some problems in obtaining a new password but in the end managed to enter the program, also activated the mods i have (besides the campaigns, for which i haven't been asked a key so far). Anyway, after completing these steps I am able to launch DCS world and get to the main screen; but from there, nothing else works, the program just sits there frozen on the loading screen. I've already performed two repairs, no dice. Any suggestion?

i've played this mission already two times without success, then came here and see about "having to land on southern side Podkova". gonna give it a try. all in all, this campaign would have been great, with no more than 10 minutes of added work. but no; it's the mi-8 and one should not expect same standards as the campaigns for a-10, mirage and so on.

there are no numbers in the qfe little window right of the baro altimeter, it is black. the qfe rotary moves two clock-like rotary indexes on the altimeter and adjusts qfe, but there's no way to tell the current qfe selection. did i miss something on cockpit setup, i seem to remember that this device was working in older versions. edit: nevermind, i found out the reason. the qfe was set so low by default that it was out of scale. this happens in the spring tension campaign, solved by turning the rotary until numbers appear

on the campaign selection screen, description for "Fortress Mozdok" is in Spanish, when English is selected by default

ok, I've been able to reproduce the problem only if my second monitor is used, in particular I was streaming videos while playing. in normal conditions, ssaa works as intended. thx for the answer.

nope. only 1.5 ssaa. got latest drivers and all. no vr headset, trackir or similar. will post screenshot as soon as i can.

was working wonderfully until the last two updates. now, it does not work (AA simply not applied) and creates artifacts (ghostlike shadow of the plane following it in external view, unexplainable darkening of certain bands of the screen)

Mission 6 ("Assignment in flight") has been broken by a bug that causes the players aircraft to spawn into another su-25, damaging and destroying both in a few seconds.

it's actually something common to pretty much all conventional helis. Not that I have been able to do that in DCS with the Huey and the Eight.

I was playing Fortress Mozdok campaign first mission, after landing I switched to my wingman external view and spotted this issue. If the aircraft has R-27 missiles loaded on the innermost wing pylons, the flaps clip through them, if extended to their maximum. Although imho it isn't a big problem gamewise, it raises some realism doubts I believe, how does the RL aircraft behave in this situation? I' d suppose that flaps are prevented to extend beyond a certain limit but I don't really have any source to confirm that. Also, apologies if it's been already reported, I scoured the forums quickly and couldn't find this so I posted it just in case.

I know this thread is a little dated, but I found that increasing gain on the FLIR helps somehow. Also, switching between whitehot and blackhot if either mode is not effectve

oh noes, I oppose this request, ED should be concentrating its resources on the B-2 Spirit. This game needs a stealth bomber! xD

so we can't hope to have realistic SR-71s and MiG-25s in the future .. :(

I have the L-39, besides the Hawk, and it's a great module. The CC101 I have not and never will. But my (unrequited) advice would be not to compare the L-39 with the other trainers - it is in fact fully made to DCS standards , and it's a pleasure to fly and operate - both the flight model and the ac systems are rendered beautifully. Anyway, I have the fullest confidence that the M2000 is gonna be a jewel.

can't say I don't agree.

no complaining intended but.. it's alarming how common the concept "pay to work" is becoming.. yaya I know, nobody forces you to do that..

bought the 2000 yesterday, was expecting lots of inoperative things so I won't complain. This AC feels pretty good and it gives out the impression that it's gonna be a very good module - apart from this, not too much to add - in fact I think I'll start learning it when there's something more in it, right now I don't believe it's the right time yet. I generally agree with the OP, but in fact I have some kind of "complain": I believe that in the latest years the terms "alpha", "beta", "open beta" and the like have been used in a very undiscriminate way. Those terms were invented by the software industry to define various states of a determinate piece of software that was still not finished - that still had not reached v1.0. I believe that having different terms to apply to an early release was made with the intent of giving users something "certain" on what to expect from the software: Alpha does not mean "This is very unfinished" and beta "this is less unfinished". I mean, the term should describe more particularly what kind of functionality has been reached and what is still undeveloped or needs debugging. Right now, seems to me that developers and software houses are basically using the terms as a warning that goes like "you are not getting the full software, and you do it at your own "risk". This is also what I can understand about the point user Brisse made - I believe he/she was asking for a little more clarity about what to expect from what's called "beta" or "alpha" etc

I thought that the mirage modeled in DCS does not have MICA capability

after 1.52 update, DCS KA-50 keeps crashing in campaign mission Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.2.48162 Application Timestamp: 566b123d Fault Module Name: Effects.dll Fault Module Version: 1.5.2.48162 Fault Module Timestamp: 56698909 Exception Code: c0000005 Exception Offset: 000000000000bee4 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 4cdc Additional Information 2: 4cdcd8ab19840e9cc21742cc71ebb24f Additional Information 3: 4198 Additional Information 4: 419840f43694dd86bbcf9cf3d7bc17b6 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt logs are attached Logs.zip

I decided to change my DCS start shortcut to "DCS_updater.exe update" - this way it checks for updates every time I run the simulator, so far a-ok