JG14_Smil

I helped a friend with one of these a few years ago and I believe he went through the same thing. Here is a pic of what to look for in Game Controllers. It appears the buttons are setup as analogs by default. If a button turns red here, but not in Helios, I would delete the Interface for it in Helios (you just use the delete key), then re-add it. I've looked for documentation but not seen any yet.

I've seen it while flying online only.

Read Post #3. That is the link to it. Good luck on your pit build.

Very interesting thread! Thanks. Helios will switch the monitors anyway you want them... it is easy as 1=2 and 2=1.

Does the Windows game controllers show buttons? They will turn red if they are working and you push the button. Have you defined the buttons as analog buttons in your setup of the hardware? If they are defined to send a keystroke, they may not show up as an analog button. Check your hardware documentation to see if this can be done. Best of luck with your cool rig!

Inventables is offering $100 off of the XCarve price for the Holidays. Would have been nice to know... :)

Hello, I am unable to connect to the server listed in the thread title. As soon as I click on a Ka-50 to fly, I am sent back to desktop. I can connect to any other server I try with no problems, in 2.0 or 1.5. I am wondering if anyone else is having trouble (it is Nov 15, about 1200 Z). Could I be banned for some reason? thanks for any answers,

yep like Capt Zeen said: two dashes are all that is needed to fix the exports. Not hard to do. It doesn't have to be his export.lua to work.

For third party hardware, look into Helios for integration. Your software gauges can come from here also.

Just to be sure: you are editing the options.lua found in the user/saved games/dcs.../config folder, correct?

Edit your User/.../saved games/config/options.lua for proper resolution and aspect ratio. Please note: You need to use Notepad++ for editing the lua files, not Windows Notepad.

Hello, thanks for replying. I fired up the X Carve and made a test cut and it looks very good. A great start. Not too loud as I was afraid of. I have learned so far: Build was pretty easy. Online instructions have errors and incorrect illustrations, but still easy to get it done. Part quality was very good. I had one threaded hole that was tapped a bit crooked. Setup instructions were a bit ambiguous, but I still did manage to get it running. Be sure to set "Advanced settings" for the Z Probe (if you use this). I bought V Carve Desktop software. You can design parts on it but it won't run the X Carve as it is not a G Code controller. You export your V Carve project to Easel (or some other controller) to run the machine. Much to learn yet here. If this was made clear to begin with, I missed it. Be prepared to learn more than one software if you are not using Easel for everything. I had to flash my card to get the Z axis to complete setup. This is done in Easel. Most X Carves bought in 2016 require this. All my axis ran backwards following the instructions. I had to reverse wires (easy to do). I found this much better than reversing the software control. Support knowledge is all located in the Forum. A lot of info there! However, the forum is a cross-linked cluster %$#. You start in one thread and end up who-knows-where, but the info is there. You have to run setup all the way through, if you try to go back, will start over. I've read of people reporting DRO (digital read out), but I have not found this yet. X Carve is alike a whole community, and there are all kinds of mods and ideas that are shared at the website and forum. I'm really glad I bought this. I used to have to work standing up in my free time at work, but can now do this at my leisure, sitting at my computer. Great hobby.

Going to re-open this post as I thought it better than making a new one. I just have to assemble my controller box and my 750mm X Carve will be assembled. I have the V Carve Desktop software and I've been spending time learning it and things are going well. I've drawn my missing panels and have started with tool paths for them. What a great toy to enjoy in my retirement. I'll posts some pics in the future as things get rolling.

I really enjoy seeing home-built cockpits and controllers. Thanks for posting the pics!

Hello, This should be in the cockpit builders section.. almost missed it here. I've recently found some linear gauges here that I would like to see if I can interface them with an Arduino card. Much easier than re-building them with servos (my original plans for them). I've already had a servo failure in my APU temp gauge I built. Have you looked at the DCS BIOS links? That sounds like an adventure, redoing it from scratch :) Would love to see pics of your setup. Best of luck with it. Cockpit building is such a great hobby.

Like I said, I have one here if you are close. I've seen them in a lot of old joysticks.

That's a pretty common potentiometer. Easy to replace it. Actually I have the whole assembly's laying around here. See if you can still solder the contact without the perf board would be easiest.

I just wanted to say "wow!". My first flights in the Mi-8 were very loud and scary... as a first flight in a helo should be. :) Scares the heck out of me as a cockpit builder too! What a great module. Kudos!

:) Thanks guys, very interesting! I wonder when it was changed. I know for a fact the NM and KM were the only units in the past. I don't think there was ever a reference to statute miles.

Hello to all, BS manual says we should have these units for distance in the ABRIS. "KM and NM". Instead I see we have KM, AM, MM. (OPTION/SETUP/UNITS) Any ideas of what AM and MM are supposed to be? thanks,

Nah, if you look at a real airplane manual, fuel data is listed in a similar way. You use the info to estimate while you plan. That is what the ABRIS info is for, estimating, not actual fuel burn. You're correct in that all the things you mention matter in actual fuel burned.

Hello, QFE setting is important when setting up a mission. If it is different than the default in the aircraft, the aircraft will slam into the ground at mission start. Using AGL instead of MSL should help prevent it.

In your saved games folder, edit the config/options.lua file to your resolution. Use Notepad++.

Hello. Be sure to use the control indicator (I think it is RCTL ENTER) to see where your controls are going when trimmed. If your helo is spinning you need to make sure HDG AP control is on. There is a lot to learning the BS AP and its quirks, but it gets easy soon enough.

In this argument, everyone is correct. Pipok, your last post was worded perfectly. I agree 100%. I also agree that ED can use realistic data and nothing else when making the sim, just as a matter of principle. The Ka-50 deserves an upgrade (again). best wishes to all,