JG14_Smil

Hello, OP is 'original post' I think. I'll be getting my VAC working again soon. It is a great tool when simming. Your profile is very complete, but I could never remember all those lines and I defer to simplicity over realism. You memory is much better than mine Strongharm. :) Agreed it is a well-spent $20! SnowTiger: I apologize for not speaking your language... "OP is 'original post', eh" :)

Pedal base is cool as heck. Seems like a lot of leverage on the plastic parts for the cyclic. Best of luck on your build. I have scrap TM parts laying around here... I think the production PFCS was plastic. Cougar is potmetal (aluminum).

Hello Gizmo, Have you gone through your UI and made sure your axis are calibrated, assigned correctly and there are no multiple assignments?

Excellent! Thank you =Andre= and shagrat.

DCS would have to be written for using a car simulator pedals (gas/brake). You would have to have one pedal go positive and the other negative. It would be a mess. Yaw is controlled by one axis only.

Hello Andre, You're making a great product and I wish you the best. I currently own and use a TFS3 seat, so I know just how important it is to feel this feedback. As I watch your development I see I will be buying one of your seats in the future. Every serious simmer should own one! I wanted to ask if you think you'll be able to tie into any exports for a Vortex Ring stall. The seats can easily produce the textures to replicate the shaking screen cockpit if they could be linked. The data spy for my seat does not show (or request) exported data for that, and instead uses an airplane stall routine, not good for helos. Other than me working on my TFS3 profile, the TFS3 is a dead project, so I know no one else to ask these questions to. Thanks again. I wish you the best and will be ordering in the future. Oh, I'm also excited to try out your sound module with my bass shakers. Lot of work to do!

Hello, I had to look twice as I use the Slippery Pete handle sometimes... :) I still get cockpit shakes in my Ka-50 and I use a TIR5. I actually try to reduce them as I am sitting in a cockpit. If my pit doesn't match that shaking it takes something away for me. I've stopped the leaning cockpit and some shaking with the G-Forces and Head movement options. Try experimenting with these options to at least learn what they do. Camera shake has nothing to do with it in my case. It's just me, but I detest that stuff and disable it all. I'm on multi monitor and externals are just not fun to watch on my PLP monitor setup. It might even be controlled by lua somewhere(?). Good luck Pete... "oh, he's a slippery one..." Kramer on Seinfeld.

Hello, The trim feature in BS is a compromise for self-centering controllers. You set the trim and return controls to center. The real Ka-50 controls do not return to center, but stay where the real trim systems sets them. My rudder pedals don't return to center, so I disable the trim in options. I truly hated having the rudder trimmer on and I'm glad it's gone. As most are! The real Ka-50 has rudder (yaw) trim. Use what is best for you though. :)

Hello, Select what items? How are you going to move the cursor around with the joystick and fly at the same time? You can map any button to any command in the UI. Go through the pull down menus and find what you want. Myself, I just un-map the mouse from the camera views. It still works for selections, but it won't affect the camera when I LALT C to hide the cursor. I don't use externals very often as I am multi screen, if I do, I can use keyboard to move the camera. Please note: using externals as you are doing is a form of a cheat and externals view can be shut off on a MP server to prevent this. I'm not judging, I'm just giving you a heads up. It is best to learn the right and realistic way. :) I can't tell what command to bind to as it is unclear as to what you want to select with the joystick button. Good luck to you,

okey doke. I'm ready to start flying again. Just need to test my TS levels and good to go for MP.

Thanks for this thread, I learned a lot from it. I just finished a flight on the 1.5 server and it was very nice. Great to see some of the differences from 2.0. Yes, wind blows there and it is a great feature.

I flew on the server you're asking about, no problems. I used my rudders. :)

Hello, Heading Hold was not turned on until after you took off. Turn t on and leave it on in your start up checklist. I don't see any rudder inputs on your control indicator. Might be because of different hardware. Anyone else see the rudder pipper move? Cold helo at Anapa?... hope so!

Thanks, I've been in the 2.0 as the Ka-50 are not cold start in the 1.5. server.

Thanks Fred, That's what I was thinking of and I can see I had it wrong. I do note I was in the aerobatics server last night. It did feel a bit strange in flight but there was no wind at all and I saw no failures in the pit either. I wonder if a random failure might have happened when you were wind-vanning? Just a thought...

Yes, it could, but it could be caused by the gyros for the navigation system not being ready. I forget the exact terms, but the wind direction in DCS is the opposite of what we use here in forecasts (wind from). Are you using the Control Indicator? I move mine to the center of my screen. It is quite important to see it when flying the Ka-50. Your Heading Hold blue AP light should always be on.

Thanks for adding these links. I used to spend time at the xsimulator site long ago. As I learn to program in the future I'll be using these links more. My 3.0 version of my pit will be built with some motion (long ways off). A little motion or tactile feedback goes a long way towards making a great pit. If it doesn't move or vibrate, you're just sitting there...

Hello again, I just found a situation where use of a " Background Fill" on the gauges monitor properties in Helios covered up the exported viewports. That might be what caused your problem. Turn off the fill if so. hope it helps,

viewporthanding.lua controls that. You fixed it when you did a repair.

Bad thing about curves is: If you take away input at the start of controller travel, it will make the curve ramp up harder towards the end of the travel. On some axis, reducing the Y Saturation can be very helpful, especially for helo controls where you don't move a controller to maximum. You can't really do this for an airplane axis as it might increase your turn or roll radius. A little curve is nice if you can get it to work for you. It depends on where you need the "sweetspot". This is no "should be" setting. Best of luck to you,

Ahh OK. That is a great start to a fun hobby. That will work fine. I'm not familiar with DCS BIOS, I use Helios for my interfaces. It lets you edit the value that affects the ABRIS (or other encoders) in DCS. It makes it easy for regular guys to use the lua inputs/output. When I retire in two weeks, I want to start working on my bucket list item of learning to program, if so, I will start learning more about DCS BIOS. good luck with your project!

Hello, I think Natural Point drivers are a separate uninstall. Check to see if they are still there. hope it helps,

AHh there you are... still waiting for the FB request. :) Yes, I have them both running now, but it takes a long time to get both synced with the pit. Almost ready to start learning again with the squad. I have to get TS running and fine tune my encoders in Helios. Oh BTW, thanks for kind words on the pit.

You edit them with Notepad++. Depends on the file, parameter and what it does.

#1 is no different than a desk. I vote #2.