Newb here help needed

What happens in external view (F2) ? Another thing - unplug your flight stick and see if the issue persists.

Sorry Viper miles away there for a while.

I have nothing connected to my pc apart from mouse logi g700 and cam which is off and not running FTNOIR.

In external view it does the same screen just rolling through north to south.

Its like the view is spinning on 1 axis constantly.

Away from my PC now so cannot post screenshots, but navigate to your Options/Controls screen In-Sim and see if there is no axis conflicts. Also, plug your mouse and camera out to eliminate them as the cause.

Strange this - never heard of such an issue before.

Ok Viper

In controls I have a few column's as follows Keyboard, Vjoystick, Razor Nostromo, Vjoystick again unsure why, Trackir and Mouse.

There controls that are duplicated across the column's especially Vjoy and Nostromo, but none of them are red.

For example for View if you were using the top hat everything except Mouse and Trackir occupy the same boxes right across the column's.

I think that Vjoy comes with FTNOIR

So I have uninstalled all of FTNOIR no need for it anymore got Trackir5 pro on the way.

Ok I feel its time for the controller to be plugged in, finally with your help Viper it seems to be working.

I think it must have been a double up of the Vjoy being in the controlls.

I have been flying around using keys which is not much fun.

So now all I need to do is work out which profile for my x52 and how to load it, I also have the pedals for yaw and brakes.

Did the uninstall of FTNOIR solve your problem?

I have profiles for the X52 for both A-10C and KA-50 if you want them or you can find many profiles in the download section.

Using that joy as well with the track IR so have set up a "center" button on the joy

As i have the same joy i have cleared everything except the axis from the option in the DCS (only for the joystick and not for keybord) and then you use the saitek software to create you proflie.

Im at work now but can take some screens and give you my profiles as posted above in a couple of hours when i get home

As i have the same joy i have cleared everything except the axis from the option in the DCS (only for the joystick and not for keybord) and then you use the saitek software to create you proflie.

 

Im at work now but can take some screens and give you my profiles as posted above in a couple of hours when i get home

Please that would be cool.

removal of Vjoy has sorted it for some reason in controls in game I had 2 column's with Vjoy not sure why.

And that FTNOIR is just a pain and I think that's whats caused my problems.

Have you installed the software for the joystick?

You should have a joystick icon down by the clock.

If you want i can link you to the correct software to download and install.

Will send you a PM with links for my profiles and instructions on how to install them when i get home.

Have you installed the software for the joystick?

You should have a joystick icon down by the clock.

 

If you want i can link you to the correct software to download and install.

 

Will send you a PM with links for my profiles and instructions on how to install them when i get home.

Thank you very much that would be nice of you.

I don't have the icon as I have uninstalled all elements of FTNOIR I think the VJoy comes with FTNOIR.

As i dont know wich windows you have here are some choices for you

Win 64-bit

ftp://ftp.saitek.com/pub/software/full/Saitek_X52Pro_Flight_Controller_SD6_64.exe

Win 32-bit

ftp://ftp.saitek.com/pub/software/full/Saitek_X52Pro_Flight_Controller_SD6_32.exe

Download this and install one of them and you should have the little joystick icon down by the clock for your X52 Pro joystick

From this icon you can right click and access all the functions and also activate the profile to use.

Sorry I forgot to mention that I have windows 7 64bit.

And thank you again much appreciated.

Any instructions for the 64bit file you attached.

I also have the Saitek pro rudder pedals

Oops sorry I thought you meant the VJoy icon, so yes I do have the icon for the Saitek and software all upto date.

In the DCS world option there should be the key mapping option and an option for the axis

Set up the axis as you want them but not the buttons on the x52-pro as those are configured in the saitek software.

Next step (this is what i did for my x52 pro and there is prob many other ways to do it) is to delete all the button bindings for you x52 Pro the easiest way i found was to highlight the column for the saitek x-52 and then just press clear

I can provide you with pictures later if you need them.

If you have say your trigger on the joystick mapped to space in the game and then you mapped it to another button in the saitek software you will have some problems.

Don't forget to do this for both A-10 and Ka-50

Thanks to Viper you're and others

I finally have control

Just need to sort out controls and load a profile for x52

I finally have control

Excellent :)

Excellent :)

How right you are I was able to take off circle the field and then land all clean no crash nice and smooth nearly fell off the end of the runway as I forgot to deploy speed brakes.

A-10 X52-pro

https://www.dropbox.com/s/4nt634n0nc3krdy/DCS%20A-10C.pr0

Ka-50

https://www.dropbox.com/s/kmsaaajo4g2tg8n/DCS%20Blackshark.pr0

Download these and put them here

C:\Users\Public\Documents\Saitek SD6 Profiles

Then right click on the "joystick" down by the clock and chose the profile you want

Here are the PDF layouts for my x52 profiles

ST Profile_ DCS A-10C.pdf

ST Profile_ DCS Blackshark.pdf

Viper

I have been reading your reply in post # 12. I downloaded DCS World and bs-2, put it into a folder on desktop and installed it into the the folder in C drive as you sait to do and then installed BS-2 (KA-50 en 1.2.3 10201_147.exe.) and when I run the program I get the message DCS has stopped working, da,da,da,da,da Close program. I have done this twice and th same thing. I did deleate the files in saved games piror to this. Any ideas?

Did you get any crash-logs?

If so, can you post the contents here? They can be opened with normal Notepad.

You can find them in

C:\Users\XXXXXX\Saved Games\DCS\Logs\

as below

Have you ensured that you allowed it to install the C++ runtimes and have you ensured that you have DirectX9c installed?

DirectX here: http://www.microsoft.com/en-us/download/details.aspx?id=8109

C++ here: http://forums.eagle.ru/showpost.php?p=997667&postcount=8

NOTE: Having DirectX10 or DirectX11 does not mean you do not need DirectX9c. They are newer, but they are separate. Thus, having DX11 installed does nothing if the game (like DCS does currently) uses DirectX9c. Fortunately, you can have multiple versions installed simultaneously.

------

Regarding the vJoys and causing the spinning - while the problem is solved, might as well explain what happened: FreeTrackNOIR (and FreeTrack) handles view input through creating a virtual joystick (vJoy). The program then interprets the camera picture and translates this into joystick commands, which are then shunted to the game to control view. (Though if I remember right this is no longer strictly necessary for DCS since the FreeTrackNOIR developers were given an API to work with.)

However, the simulator itself is unable to know the difference between a "real" joystick and a "virtual" one: they are all presented as simply a joystick. I believe there are two of them since it requires many axes - for full 6-degrees-of-freedom it would be 6 axes - and a standard virtual stick has 3 (stick+throttle).

Most likely one of these virtual axes had a funky standard position and was sending constant commands to the simulator, and being virtual and not hardware it needs to be "virtually" unplugged. Don't know for sure whether the FTNOIR software supports that though.

Yes, They are posted. I did install DirextX9c, from the install and also C++, but however when I do that I get a message that says there is a more current program installed on this system. see attached

Problem solved I was pointed to a problem with 32bit OS and that fixed the problem.