SWE-Timberwolf

I'm having the same issue. Incidentally I also use an X-56. Among the things that randomly switches on or off for me is gears, hook, refueling probe and night vision goggles. I have all these bound to my flightstick. I made a test profile for the flightstick in the logitech software (just asigned a letter to each button) then opened notepad but nothing happened (unless I clicked a button my self, then it typed the letter in notepad) However there is one more thing that switched on or off and that is the radio and I do not use any of the flight-stick buttons for that. Or to be more precis the radio switches from GUARD to MANUAL at random times. Ignore the part with the radio. After some more testing I realized that it was caused by the Voice Attack addon VAICOM PRO. However during the same time I also noticed that my master arm switch turned off and I do not have that bound to my stick either.

I see the same, I can't scroll in menus or on the map in mission editor either.

It would be really nice if the added support for this. :)

This is just work in progress https://www.facebook.com/photo.php?fbid=10155720071107651&set=gm.1918869491572392&type=3&theater&ifg=1

Hi guys! Is anyone able to bind eject to a button on your flightstick? I am not able to bind it to anything except for a keyboard shortcut.

Now I don’t usually fly the A-10A or F-15C, but have you made sure that nosewheel steering is on. I don’t remember if you have to do this on these two aircraft, but you have to in the Su-27.

Another tip would be to begin with the su-33 instead. As it has auto throttle is is a lot easyer.

I had a similar problem before, but that was becouce my computer was 7 years old. If your computer has good performance there might be a problem with the installation. Have you tried to remove all mods and do a repair?

5 minutes? What hardware do you have, do you have DCS installed on an SSD?

Haha, I’ve got to have that on my phone!

Ok, the issue is solved, sort of :-) Installed DCS on my other computer and created the lua file there. It worked fine on that computer. I then copied the skin over to the computer that I normally use and now it worked as it should. Must be something wrong with my installation of DCS.

I have tested a bit more. I have repaired DCS, removed all mods, did not help. I then tried to copy an already existing lua file from another skin and renamed my dds files to match, this worked- But if I change anything in the description.lua file it won't work any more.

Hi! Im having a bit of a problem creating a new skin for the MiG-29A. It will show up in the list of avaliable skins but when I click on it nothing happens. Normaly when there is an eror you will see the green skin, but not even this showes. I have made several skins in the past and this is the first time this has happend. It is the same in both sable and open beta. Does anybody have an idea of what might be causing this?

San Francisco bay area would be nice. That way you could recreate the old Amiga flightsimulator F/A-18 Interceptor :-)

Just tested the MiG again, just to be sure. Definetly not placebo. It is much easyer to fly now then the first time. If it had nothing to di with the axis controls then I do not know why it started to behave differently for me. Maby I am doing somerhing differently now then the first time without releasing it.

Have you tried to re-assign the axis controls as I have sugested before?

I noticed the same thing when I first tried it, almost impossible to fly. I then tried to clear all the axis controls and re-asign them. After that it was about as stable as the Su-27. Give it a try if you haven't already done so.

It would be nice if all aircraft was available for every country. But if you for instance want to be able to fly the Su-33 for USA, you should use US air-force aggressors instead of USA in the ME. The aggressors have access to all aircraft.

Just thought i give him a workaround if Heatblure does not have time to answer or if the answer isn’t what he hopes :)

That would simplify things alot if we could have the time for sun up/down and the possition of the sun.

You can always program your X-52 outside the game in the tool that comes with your flightstick. There are 3 different modes on it that allow you to program each button with 3 different commands. So you can program it with the commands you need for the pilot in mode 1 and for the RIO in mode 2 l. Then you can just switch between them when you need.

What pixel density are you using? I used to have difficulties spotting aircraft and missiles, but once I lowered pixel density from 1.5 to 1.0 it was much easier. Sure your instruments in the cockpit won't be as sharp, but they are still readable.

It sounds like you should try and use the rift more often. The first times when I used the rift with DCS I also felt a bit sick. But after playing DCS in VR everyday for about a week, I did not feel sick anymore. The more you use the rift the more your head gets used to it. I even tried to set all graphics options to max including pixel density to 2.5. I had between 7-12 FPS, completely unplayable but I did not get sick :)

15fps sounds very low, thats about what I am getting with everything on max in VR. Have you tried to turn V-Sync off and AntiAlias down to 2x? Any fps problems if you run a benchmark program (just to rule out hardware as the cause) like Unigine https://benchmark.unigine.com/

What do you mean with less clarity? I think it is easier to see details in VR with deferedshading on. Before I had to set pixel density to 1.5 in order to read the instruments. Now I can read them while having pixel density set to 1.0.