Frusheen

All up to date. Just installed the Gazelle. It's very strange. I've no idea what else to try.

ED distribution.

1.5Beta won't detect CV1 Guys my CV1 works fine with 1.5 and 2.0 but will not work with 1.5Beta! I wanted to try the Gazelle in the Caucasus Map. I have Unknown sources allowed in Oculus Home and detect Oculus Rift enabled in DCS. As I said works fine in 1.5 and 2.0 Anyone got any suggestions. I've already tried a repair. The detect Oculus rift flag is 'true' under options.lua I've tried with Oculus home open and Oculus home closed. I just get DCS on the monitor. Any suggestions welcome.

Capt Zeen thank you so much for your help. I have zero experience programming but with your help I have written the following code snipet which is returning the values I need in the Witchcraft console. Thanks to Ian for that utility :thumbup: function AircraftType () local myInfo = LoGetSelfData() local CurrentAircraft = myInfo.Name if CurrentAircraft =="TF-51D" then local MainPanel = GetDevice(0) local Slipball = MainPanel:get_argument_value(28) return Slipball elseif CurrentAircraft == "Su-25T" then local Slipball = LoGetSlipBallPosition() return Slipball end end local User1 = AircraftType() local pitch, bank, yaw = LoGetADIPitchBankYaw() local accel = LoGetAccelerationUnits() return (string.format("%.4f; %.4f; %.4f; %.4f; %.4f; %.4f; %.4f;\n", pitch, bank, yaw, accel.x, accel.y, accel.z, User1)) I wrote this on my laptop which does not have modules installed. If you think it looks correct I will expand it and test it on my PC where I have my full DCS install. Here is an example of the values in the returned string: 0.0847; 0.0020; 5.5755; 0.1363; 0.9817; -0.0001; 0.0018; Obviously the final version will be output over UDP. I just did it this way to test. I think these seven values should give me all I need for the G-Seat. I think the AircraftType function should be run just once at mission start! Is that correct or may it be left as is within AfterNextFrame? EDIT I should add I don't think I require the turn pointer. The slipball value should suffice

I got one as well and tested it with cv1 using the blocks demo. It's nowhere near accurate enough for cockpit interaction. The current look and click implementation in dcs 2.0 will be so much faster than faffing about with leap. If they just remove the laser pointer from view when it is not over an active switch, knob or lever it will be good enough for now.

Thanks Capt Zeen, That's what I was afraid of. It's going to take some work for me to figure this out. Is there an easy way to live view and debug the output from the export script while the game is running? So I need to define two user variables and populate them based on the aircraft type being flown. Sorry if they are not the correct programming terms. I'd love to try and learn to do this myself as I'll be hoping to add the gazelle and also the bo105 in the future. The G-seat is purely for helicopters. I'll study some of your export scripts for Helios and try and get my head around it.

I'm looking for some help finding some variables for a custom export.lua file for my G-Seat (link in my signature). I'm already exporting six values and the plugin has room for nine in total. The custom lua script I'm using is part of the dcs plugin created for sim tools (http://www.xsimulator.net) The current variables defined in the lua are: local pitch, bank, yaw = LoGetADIPitchBankYaw () local accel = LoGetAccelerationUnits () The problem I'm having is when flying helicopters I'm missing some forces. In a stationary pirouette in the Huey for example I have no lateral force. I think the values of the slip ball and turn coordinator would give the required values needed to apply these lateral forces to my seat. Can anyone explain how to call these two variables in the export.lua script? Do they vary between aircraft? Sorry I'm not familiar with lua and from the snooping I've done through some Helios export scripts it appears to me these variable names may differ between aircraft. Any help appreciated.

Is rift still working for people since yesterday's update to 1.5 beta? My rift is not being detected. No problem in 2.0.

Delighted to hear the gazelle has been added. Great work guys.

I got sim tools working with dcs and also managed to get my Arduino code dialed in for good response to commands. Unfortunately the mxl belts and pulley arrangement for the potentiometers isn't going to work out. The belts will occasionally skip on the pulleys during fast direction changes. I added some idler pulleys to increase surface area and tension but it hasn't helped. Increasing tension any further just adds too much drag. It's back to the drawing board and time to find a spur gear arrangement instead. It's proving difficult to find gears that offer a similar ratio with the correct bore sizes. I found one source but the prices are absurd. I'll report further when I have more to show. For anyone considering a build stay away from mxl belts. They just aren't good enough in this application.

Hi Hannibal. It's still currently 0dof :helpsmilie: once complete it will have 4 axis with all 6dof represented by pressure (surge and pitch are the same axis and roll and sway are the same axis). As in real life these axis apply pressure to the body in the same way. There is more info in my build thread linked in my signature.

I got this working. Now I need to figure out how to combine it with Simshaker.

Contact Andre

Guys anyone using sim tools that can test the current dcs release? I'm having trouble getting any info from dcs with the provided export.lua script. It patches to the scripts folder but sim tools tuning utility is not receiving data from the game.

Hi guys, I'm trying to test sim tools plugin for my g-seat but I'm having an issue. I patched the game using the sim tools utility and it created the export.lua in my scripts folder. Unfortunately it's not showing any values when in game. It also overwrites the contents of my existing export.lua removing my Simshaker settings. If anyone has it working could they let me know or share their lua script. Thanks.

Be sure to connect pin 4 to ground -pin8. It reduces the fan speed but still allows for temp sensing and the fan to ramp up if needed. Without doing so the power supplies are very loud. It will also help to pick up some RC patch cables. Once cut in half they are perfect for connecting to the control pins and soldering a switch etc. You could add a little hot glue to make a 9pin plug. http://www.fast-lad.co.uk/store/mik4141_patchcable_vbar_receiver_(120mm)-p-7096.html

Poor Sven. It's obvious he's in shock at the fact that Wags made it through flight school.

Thanks guys. Anton it sure is solid. Damn thing weighs a ton. I'd love to have been able to build with aluminium but there's no way I would have managed to weld it. I struggled enough with steel ha. The weight of steel in this thing really mounts up. I'm glad I fitted casters! I hope to make the seat base actuators on a slide in platform like what I did at the rear. It will be a tight squeeze though. I really don't want to have to lug this entire thing up and down the stairs to the garage again! I purchased a few idler pulleys which I will mount at the potentiometer belts to take up some slack. This should provide better engagement between the belt teeth and small pulleys and avoid any possibility of the belt jumping. It will take about a week for them to arrive. That should give me time to get to the junk yard and get the two remaining wiper motors. Unfortunately the four point harness I purchased has its length adjustment at the ends rather than nearest the buckle. That will likely result in interference with the sides of the seat. I may have to try my hand at a bit of sewing! The things we do..... :crazy:

You can use Viacom for the radios. See the thread in the input and output section of the forum. An alternative is a third party mod which allows you to increase the size of the font and its location on the screen.

I have completed the electrical power system for the base and back rest actuators. I added pictures to the first page to show the progress. I ended up going with separate power sources for each rather than running the supplies in parallel.

No PC can currently maintain 90fps in dcs world on medium settings in VR. Hopefully further optimization to the game engine will improve things.

I have moved from the garage back to the PC to work on the wiring. Updated the first page with additional images.

Numpad 5

Leap motion is available. It is well implemented in FSX using flyinside but reports suggest it still lacks the ease of use of a mouse.

Have you a link.