SnapRoll

Hi discwalker Thanks for your post, I was thinking I was stupid... :-) Do you constantly get this problem or do things change after restarting DCS?

Tried to reproduce, but now after restarting it works like a charm. Strange... sorry, this thread can be deleted.

I cannot land on Kuznetsov any more, and just explode on touch down. Anyone else having this problem?

As the title says, external cannon sounds seem to be much more quiet than before...

Would be great if the VRS setting was also customizable at which vertical speed things start to shake. Just checked, there is no visual clue that the tail wheel retracts a bit and this is from the Manual: In the early series of Spitfire IXs, the tail wheel did not retract, while in latter models the rear gear leg folded upwards and fit into the fuselage, closed off by hinged doors on each side of the hatch. Strange that they have logic there... How can I get hold of a beta release? Is there another download site than Andre's

Thanks for your quick reply! Not that I know, but I would assume that each type of helicopter got it's ETL at a different range. In any case, it should be set to what is happening in the sim. It gives a very odd feeling when the cockpit is shaking and the JetSeat does noting, and then when the visuals stop the JetSeat kicks in. Would be great if each heli had a user tunable speed setting for ETL in SSA. As for the tail wheel of the Spit... not sure what you mean, the Spit cannot retract it's tail wheel, it is always out.

Hi f4l0 I’ve just received my JetSeat Sim Edition and noticed a few things in SSA. Spitfire: Gear Turbulence gives permanent vibration, even when gears are retraced. When at high speeds >300MPH, and you pull back the stick too far you get these cockpit shakes short before it starts to flip the plane over, but SSA does not output them. Also when you break the wings because of that, nothing happens. Mi-8: Translational Lift effect is running at around 30-50Km/h, but the cockpit shakes between 50-70Km/h. I tested this in DSC 2.5

Yes, when I start an F-5E instant mission, after pressing the FLY button, everything freezes up. Only a reboot solves this.

After today's update, all air start instant missions start with a non-rotating rotor.

I can confirm, I got the same problem. After today’s update the Spit got no more power. It seems the propeller got no pitch at all. When you move the throttle lever back and forth you will not even notice any torque effect. I got no mods installed.

Thanks for all the answers and tips I didn’t want to start a big debate ???? I can see now that without Autopilot or with AP in Director Mode all works the same like in the Mi-8, a short press resets the neutral point to the current stick position. In Autopilot mode one needs to do a long press as not to fight against the Autopilot, and once at the desired stick position release the button. Like this all works well! I also noticed that the reason for this over correcting in autopilot mode actually comes from the fact that when you fight the autopilot your stick deflection ends up to be about twice as far as when you would do it in Director Mode or when holding the trim button.

I had the same problem since the Win10 Creators update got installed and then Thrustmasters DeviceManagementApp.exe had a problem with some Windows program. The thing is I can’t quite remember but I now found this far back in my Windows System Log. The application \Device\HarddiskVolume4\Program Files\WindowsApps\Microsoft.WindowsStore_...\WinStore.App.exe with process id 12220 stopped the removal or ejection for the device USB\VID_044F&PID_0404\00000040. I think this is what it was, and since I removed the WinStoreApp I hand no more problems. Check in your Windows log first…

Hey guys, just a quick question. Is there something wrong with the trim function? I have just started learning to fly the Ka-50 and trim seems to behave strange. I would expect when I move my stick to a position so the nose is down, let’s say, by -10 degrees, press the trim button and move my stick back to neutral, that it kind of stays at these -10 degrees. But what it does it seems to over correct like double and then the nose goes down somewhere in the region of -20. This happens when I do a short or long press. With the long press you just have the chance to correct this, so when you release the button your pitch is where you wanted it. This only happens when the Autopilot for pitch and roll is engaged. Without these Autopilots everything seems to work fine and I actually got a more stable flight. I’ve been flying the Mi-8 for almost a year now and there it works perfectly. I would have expected it to behave the exact same way here… Am I missing something? I haven’t finished the manual yet, but searched for trim and I found nothing described like this. I tested in in the Beslan take off instant mission in 1.5.8 and 2.5OB Any help would be appreciated.

I have just noticed something myself. When I quickly go into the F10 map and then go back into the cockpit most of the texture is missing and it takes several seconds to come back. This effect seems kind of stronger the more you zoom out in the F10 map. This only happens to landscape, over Vegas, I did only notice it in the far distance. This might be what you are seeing but you might have another problem that exaggerates this. Does anyone else see this happening?? Tested it in Spitfire free flight instant action. Got a GTX1080, 5.6GB of 8GB used, 64GB RAM, resolution 3840x2160,

One more Thing: Delete the metashaders and fxo directories in your Saved Games folder: C:\Users\yourusername\Saved Games\DCS.openbeta

Hey there… what I posted is not a fix! It is just a test to see if it could be your hard drive. You got red errors because you blindly copy/pasted my commands. What I posted is the default path. It seems you got DCS installed on another drive, so adjust the path according to your environment. Your SSD is perfect, as is the rest of the hardware specs you posted. You should not have any problem running DCS on this hardware. Here is what I would do: Run my test just to see how it goes. (I am interested myself) Check if your Saved Games folder is also on an SSD Update Windows Update all your hardware drivers Repair DCS

Hi, I got a very similar system and Nevada runs super smooth on my box. You have not written about your hard drive you are using. Is it an M2 drive? Have you installed the appropriate NVMe driver? Is it DCS 2.5 OB you got installed? Since you got the same ridiculous amount of RAM like I do, try to load all Nevada terrain files into memory first to see if this changes anything: Open Task Manager --> Performance Tab --> Open Resource Monitor --> Memory Tab Check the Standby Memory: mine is 6032MB after boot Open a “Windows PowerShell” and do the following: cd “C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains” get-childitem -recurse Nevada | select-string a | out-null While this command runs, check in: Task Manager --> Performance Tab --> Disk 0 © How many Megabytes per second do you get there? I get between 18 and 23MB/s most of the time. Let the above command complete, mine took about 30 minutes. Once complete, check the memory tab again. Your Standby Memory should have risen by about 34GB. Mine was 40655MB after. Now start DCS and fly in Nevada. Since all files are now in RAM, in theory, it should mask any hard drive bottlenecks. But then, I do not know if my trick works, it is just a thought I had, but if it works, then there you go, you got a problem with your hard drive or driver. Cheers

Sometimes I see some weird green patches underneath trees. They disappear as you get closer. 2.5.0.14138

There is bad weather in the 3rd Epsom Campaign mission, but the mirror shows perfect sunshine. 2.5.0.14138

At certain angles there is no pilot shadow visible. It seems to be overlaid by some other object. DCS 2.5.0.14138

There is a patch of land just North West of Azeville without any trees and things, just basic texture.

When you shoot into the water you see shock-waves go through your sight glass or HUD and distort everything. Here an example from the Spitfire.

My update worked perfectly! I had all 3 versions installed: 1.5.8beta 1.5.8stable 2.2alfa I've now updated 1.5.8beta to 2.5beta and let 2.2alfa be removed. Since this merges 1.5beta and 2.2alfa, adds some and replaces a few files and gets rid of duplicates... It basically turns out to use up about 35GB less disk space than before. My 2.5beta is now using 99GB in total. I have the following modules installed: FC3, Mig-21, Mig-15, Mi-8, BS2, Huey, F-5E, Spit, Mustang, Nevada, Normandy and pretty much all Campaigns for these modules. Keep in mind that it downloads first and then unpacks the files, so temporarily you would need some more space. I did not sit there and watch the thing but I would recon you need at least 20GB of free space. Don't quote me on the numbers, I cannot exactly remember how much free disk space I had before.

Hi all I got a little workaround for those of you who use a TM Warthog with the Target software. This fires off a sequence of tiny key strokes as long as you keep the button/hat pressed. The good thing about this is that you are able to let it be pressed for only once and for only a short time (20ms in this example). The delay of 100ms helps for getting your fingers off the button/hat before the next key stroke happens. Obviously, the wheel now turns much slower, but you could define multiple different speeds and use a modifier if this is not good enough for you. Put these lines somewehre after: SetKBLayout(KB_ENG); int Trim_left = REXEC(0, 100, "ActKey(CHAIN(KEYON+DOWN+R_CTL+',', D(20), KEYON+UP+R_CTL+','));"); int Trim_right = REXEC(1, 100, "ActKey(CHAIN(KEYON+DOWN+R_CTL+'/', D(20), KEYON+UP+R_CTL+'/'));"); Use your own definitions here, mine changes the view per default and when used with the modifier switch it trims for all 3 layers: MapKeyIOUMD(&Joystick, H1L, Trim_left, KP4, Trim_left, KP4, Trim_left, KP4); MapKeyIOUMD(&Joystick, H1R, Trim_right, KP6, Trim_right, KP6, Trim_right, KP6); Don’t forget to remove the original H1L and H1R lines. Cheers

Hi all This is my setup I've been using for quite some time and it served me well. FLAPU Press Flaps_up [L_CTL f], Pulse, 100ms Flaps_up [L_CTL f], Pulse, 100ms Flaps_up [L_CTL f], Pulse, 100ms Flaps_neutral [L_SHIFT f], Pulse, 7000ms Release Flaps_down [L_SHIFT f], Pulse, 100ms FLAPM --> no action --> FLAPU-release does this job FLAPD Press Flaps_down [L_SHIFT f], Pulse, 1500ms Flaps_down [L_SHIFT f], Pulse, 100ms Flaps_down [L_SHIFT f], Pulse, 100ms Flaps_up [L_CTL f], Pulse, 7000ms Flaps_up [L_CTL f], Pulse, 100ms With these sequences you basically do everything needed to move the flaps up and down, including the waiting in middle position before fully extending the flaps, as well as putting it into neutral after fully up or fully down. The drawback is that you should not do anything while these sequences are running, otherwise it can get out of sync. There are two possible ways of using the flaps: 1. Middle position and up again, this is used for takeoff. 2. Middle position and immediately or later fully extract and in the end fully retrieve. This is normally used for landing. - It is not possible to go from fully extracted to middle position. Here is what you have to do to get it in sync with the flap lever and keep it in sync. - Start the Target profile and wait 10s before starting a mission - After a full down or up, always wait 10s before touching the flap switch again - Do not do any other things on the keyboard during these 10s. - Ground test your flaps and adhere to the previous three points. If you up-down-up-down-up-down the 3-Pos switch very quickly, you obviously fire off the sequences multiple times with no definite outcome. But... by just fully extend and retract the flaps, you get the sequence in sync with the lever again, if you keep the 10s in mind. This is why there are 3x up and 3x down to always do the full travel possible, no matter where the lever is. Enjoy...