Bungle_uk

Wow, that was quick Innerloop, Silver Dragon, didnt even have time to edit it before you posted :D Thx anyway hehe

Wanted to check something on the blackshark last night and went into the doc folder to find no manuals. Were they moved some place else or have been overlooked? Edit: Nevermind, found them in the mods\aircraft folder.

Not sure how the CH is set up, i.e. if it has seperate USB connections for each section or if there all combined into 1 controller. Hopefully though this will help you. Open up the options section then: 1. Select controls 2. Select the relevent airframe (e.g. A-10 sim) 3. Select axis commands 4. Select appropriate control (e.g. rudder) 5. Double click in the column of the controller you wish to assign the rudder to 6. Move the axis you wish to control that function (In this case the pedals). You should see the relevant axis in the Button/Key section e.g. "Slider 1" or "X axis" 7. If you find the axis is the wrong way round E.g. left is right then select the Axis tune. You can invert the axis here or adjust sensitivity and deadzone etc.. Repeat for throttle etc.. Hope that helped ;) Note: You will need to repeat this for each airframe in DCS World, this is intentional to allow you different setting for each aircraft.

Have you guys tried assigning the microstick directly in A-10 under axis commands? it works well for myself in A-10

I wouldnt recommend using the logitech profiler to configure your controls to DCS. Instead I would leave everything as directx buttons (Default) then use the DCS mapping in game to assign the controls. Granted its going to take a little bit of effort to map each control that you need but the + side is that DCS has its own control set for each airframe and its also quite powerful in that you can adjust response curves / deadzones and even assign a button to be used as a shift to effectivley double or even triple the no. of buttons available to you.

The pylons should be transparent. Located on Mozdok airfield. Specs/drivers etc.. in sig Blackshark 1.1.1.1

When attempting to create a 4-ship flight on the Kuznetzov carrier, 3 issues arise: 1: only 3 of the 4 aircraft will spawn on the carrier deck 2: when attempting to land a 4-ship, they wont taxi to the correct location after touchdown creating a traffic jam 3: When deck is blocked aircraft just keep coming and crashing into the back of the previous aircraft. 3 ship and less flights appear to be ok DCS Blackshark2 1.1.1.1 1. Processor - Intel q6600 2. Motherboard - Asus P5E3 3. RAM - 4 GB DDR3 1333mhz 4. Video Card and Driver version - Sapphire 5850 Vapour-x driver 11.9 5. Type of CD/DVD drive - DVDR 6. Internet connection type and performance - 10Mbit down/1Mbit up 7. Control devices - HOTAS Cougar/Logitech G-25 8. Operating System and installed updates/service packs - Windows 7 64bit pro SP1 9. DirectX version - 11 carrier test.miz carrier issues.trk

For some reason DCS removed the ability to have both a modifier and a switch function in BS2(this was present in BS1). I dont know why that has been done otherwise you could have used that system. Maybe a dev can chime in on that one. But to be honest, the Shark doesnt have so many controls that you need to get at quickly and using the shift function is more than adequete I find myself to create enough functions on the stick, note I am using the cougar though but I believe the Saitek has about the same buttons available.

What he said. I actually use the G25 pedals as rudder pedals with combined axis. Also, in options/misc make sure the "force feedback" option is unticked. Otherwise you will have trimming problems

correct :( Its the downside of having everything seperated like it is. The advantage is using less resources as your only modelling one thing at a time.

A really good article that might interest you on rockets: http://www.simhq.com/_air14/air_508a.html

Thank you for the solution shamandgg. This was driving me nuts and it seems this doesnt effect all for some bizzare reason

Found a solution here: http://forums.eagle.ru/showthread.php?t=71587 Clearly this doesnt effect everyone

Post updated with comparisons. Hmm, maybe I need to go natural point then and look there. Thx

Thx for the quick response Sobek. All is set as you stated. Lost the attatchments tho so pictures may help to get across what I am trying to say.

Ok, here we go, I'll try and explain this the best I can and hopefully you'll all know what in gods name I am on about. :) DCS appears to read TIR in a different state than track IR actually is. Lets say I turn my head left to check my 7 o clock. The game thinks I am looking 7 o clock, however TIR thinks I am looking 9 o clock (based off the little head on TIR screen) If I turn further so TIR shows I am looking 7 o clock, the game thinks I have gone all the way round to my 4 o clock. Now of course, I could just reduce the sensitivity of TIR a little which would be all well and good. However, it has an effect on the 6 DOF as well So when looking at my 7 o clock and I want to look round the edge of the seat, I move to what I think is my natural right but the view moves forward in the pit (towards the HUD) This is of course because TIR thinks I am looking at my 9 o clock and not 7 o clock. Its not a huge problem but its somewhat off putting. Am I the only person with this problem or are there more of you out there? More to the point, what (if anything) can I do about it? This happens in both A-10C and Blackshark 2 Apologies if this has been raised before, did a quick search but couldnt find anything specific to this. Some further pictures of TIR and DCS

there is a template in the editor for the sa-10 and patriot, works very well I must say, just use one of those then position the units accordingly.

I believe they are ADF frequencies (Automatic direction finder)

Multiplayer flight by any chance? IIRC they move fine offline and on server but not for clients

Thx for sharing, was struggling with it myself :D

setup fine, only adjustment was the speed, changed from 175 to 250 (remember, this is ground speed not indicated air speed). at 175, you will be close to stall speed at 14000ft (about 130 indicated) with it at 250, had 200 indicated for the tanker. would also recommend raising the altitude as theres not much clearance to the mountains (18000ft maybe?) tried in MP, got connected and took fuel no problem, I was however the only one in the server.

Once I recieved the co-ordinates from the JTAC e.g. GG467775 1. create a new waypoint in the CDU waypoint page (?3) 2. enter 37T in the scratchpad then press OSB 17 on the CDU page(4th one down on the left) 3. enter GG467775 in the scratchpad and press OSB 16 on the CDU page(5th one down on the left) 4. change waypoint selector from flightplan to mission 5.select waypoint 3 for your target (or whichever number it was you created at step 1)then proceed with comms to JTAC you may also want to add the elevation data too Hope that was helpful

WTM is a co-ordinate system same as latitude longtitude. Take a look at page 458 of the manual for more detail. From the manual "The world is divided into large grid zones. They're given a number from 1 to 60 based on their east-west position (longitude) and a character based on their north-south position (latitude)."

I think I got it, it was because I had to change the WTM zone from 38T to 37T. There is a zone change that runs right through Senaki which was causing the issues.

in his original post ;) I have had some issues too, sometimes he will talk to me sometimes not. Sometimes the WTM co-ordinates are 840 miles away sometimes ok. This stuff is still fairly new to us so it could be something I am missing too.