Tactile Feedback System 3

[acemark]

My File for KA-50,TSF 3 and Helios.

Export.lua

[G00dnight]

Export.lua

my export file..

 

tom are you trying to use separate exports for a10//ka.

my export is an all in one but you will need these other files from peter p's

 

All_Exports_ON_for A-10C_and_Ka-50_in _DCS World_1.2.0.zip

Edited January 26, 2013 by G00dnight

[TomDK]

Thanks to you.

 

 

Yes, I am running PeterP´s files ! Works great.

[G00dnight]

OK so is your prob solved or do the gauges still not work ?..

have you tried a new profile with just one gauge on it ?..

I cant get that you cant add KA interface in your profile..

[TomDK]

I tried your files:

 

With acemarks´s file:

A-10 C works with helios and IVIBE

KA-50 works with helios but no IVIBE

 

 

With Goodnight´s file:

A-10 no helios , no IVIBE only the exports to see

KA-50 helios with exports but no IVIBE

 

 

And a screenshot from my helios ...

Edit: I could update my export.lua via helios, it accepted KA-50 and also A-10. But .. if I activate A-10 the export.lua is changed to port: 8068, if I update KA-50 the port is changed to 8069 !!

 

EDIT: TFS3 Software says : No game started ... so it realises no output data from DCS .

Edited January 27, 2013 by TomDK

[TomDK]

Mhhh ...

 

This issue must be something with the ports setup and Helios.

 

If I load my shark-profile in Helios Editor it tells me: Path to KA-50 not found). If I open the device KA-50 and point to /DCSWORLD/ and they update my export it telles me "DCS updated".

 

I set for A-10 and KA-50 the Portnumber in Helios Editor to 9089.

Both profiles work with one export but no IVIBE.

 

IVIBE use

outsim_port = 10001

outgauge_port = 10002

outsim_autostart = 11111

 

There is somwhere a problem with the ports I guess.

[G00dnight]

well its got me beat..

all I can say is that since using peter p's files I have not pressed update for anything in helios, I just point the editor interface to dcs world and then save the profile I DO NOT PRESS THE UPDATE BUTTON. I think you need to copy new export file from peter that has not had the helios update done then just point and save..

BTW the export I sent you is the one I am using I have I-Vibe in a10-ka-p51, exports in a10-ka, and helios gauges in a10-ka. not done anything with helios in p51 yet.

 

oh one more thing my interfaces always say not set up but they work go figure that one out.

Edited January 27, 2013 by G00dnight

[TomDK]

Thanks again ...

 

I spend now 3 hours in my pit with no success.

I downloaded and installed the "shark and a-10 export.lua" with the result that helios will not work and the ivibe will not work.

 

My "best result" with 2 different exports.lua is:

 

A-10 with IVIBE and Helios

KA-50 with IVIBE or Helios

 

Strange is that I start the Helios-Editor, load a KA-50 profile and it says:

"DCS Black Sharl installation path was not found"

 

I think there is my problem ...

 

Strange enough that your files do not work in my system. Maybe I will install all the stuff again :cry:

[schkorpio]

hey guys, can anyone provide any info on how loud this TFS3 is? I bought a buttkicker gamer v2, but it is way too loud, so i can't use it :( (i know its got adjustable settings the the BK is either too soft to feel the subtle effects, or its shaking the entire apartment complex when I fire the GAU-8, don't get me wrong, its awesome, and if I lived alone it would be fine.)

 

I'm looking for something that actually works with headphones - and is quiet enough not to disturb someone in the next room let alone next apartment.

 

I'd post on the TFS3 forums, but it looks dead there lol

[TomDK]

No noise ! Just vibrating.

[schkorpio]

Cool, thanks Tom. I will save up for one in that case :)

 

btw, that cockpit is coming along very nicely :)

[Cowboy10uk]

Hi all, I've Been following this closely, and I have a few questions if you guys don't mind answering them.

 

1. I use the Astro A40 headset and max amp via optical for my sound, since TFS3 uses LUA files for its information, am I right in guessing that it will work with this setup and will not need to pull sound from the motherboard via the speaker socket. ( buttkicker won't work anymore as I can only output to either optical or speaker not both )

 

2. I currently run Helios for both my KA.50 and the A10, using PeterPs stunning combined LUA file, has anyone managed to get TFS3 to work with this. Looking at the forum I'm getting the impression that it will work with either A 10 or KA50 but not with both on a combined LUA file. ( this is the major block at the moment, as their is no way, I'm prepared to give up Helios. )

 

Hope to hear from you guys soon.

 

Cowboy10uk

[JG14_Smil]

Sounds like a rattling bag of bones.

 

hey guys, can anyone provide any info on how loud this TFS3 is? I bought a buttkicker gamer v2, but it is way too loud, so i can't use it :( (i know its got adjustable settings the the BK is either too soft to feel the subtle effects, or its shaking the entire apartment complex when I fire the GAU-8, don't get me wrong, its awesome, and if I lived alone it would be fine.)

 

I'm looking for something that actually works with headphones - and is quiet enough not to disturb someone in the next room let alone next apartment.

 

I'd post on the TFS3 forums, but it looks dead there lol

[PoleCat]

New info on setting up the TFS3 in 1.2.3

 

http://forums.eagle.ru/showpost.php?p=1692130&postcount=16

 

Out

[Sov13t]

1. I use the Astro A40 headset and max amp via optical for my sound, since TFS3 uses LUA files for its information, am I right in guessing that it will work with this setup and will not need to pull sound from the motherboard via the speaker socket. ( buttkicker won't work anymore as I can only output to either optical or speaker not both )

 

Cowboy10uk

 

I run A40s, when I fly I switch to analog output which goes into the mixamp via the MP3 hook up. It is a seamless transition between "flight mode" vs "optical mode".

 

Buttkicker works off of the analog Y while TFS runs off of USB -- I run both simultaneously.

Edited March 5, 2013 by Sov13t

[Hawk_5]

I....just....have....to....get one!

 

I have a basic feedback system in my chair but the TFS3 looks awesome!

[Cowboy10uk]

I run A40s, when I fly I switch to analog output which goes into the mixamp via the MP3 hook up. It is a seamless transition between "flight mode" vs "optical mode".

 

Buttkicker works off of the analog Y while TFS runs off of USB -- I run both simultaneously.

 

Now that's a great idea, didnt even think about that. I'm assuming I just swap my audio input in windows when I go flying. :thumbup:

 

Will be trying that tonight. Thanks.

 

Now fingers crossed the combined Helios compatability is fixed and then will be very tempted.

 

Cowboy10uk

[pgh2atl]

Does anyone know if these are currently shipping? I placed an order this past week, requested a shipping ETA to Craig & haven't heard back anything back. I've read around about delays so wanted to get some feedback from recent purchasers. I don't mind the wait, but also wouldn't mind some kind of response from the company. :(

[recoilfx]

Hey all, I've played with the TFS3 for awhile now and noticed some bugs with the native IntelliVibe support. I've reported them but so far it seems that the IntelliVibe forum is unresponsive. Instead, I tried to fix these bugs by customizing my own LUA export code.

 

So here are the chief complaints with the native IntelliVibe support:

 

1.) The G load effects are wrong as they are aligned to the world axis, not the plane axis. What this means is that when pulling the plane straight up or down, we get the G effects, but if we turn the plane 90 degree side ways, then pull hard and stay in the same altitude, we get no G load effects...

 

2.) Engine power is tied to RPM. This doesn't work well with planes with constant speed propellers. The P-51D reaches full 3000 RPM with less than half of the throttle, so you don't feel more oomph from the TFS as you go past second half of the throttle.

 

3.) Stall boost is poorly modeled. It's based on air speed and throttle settings. (IE. Stall effect comes on when the air speed is less than 100 mphs with throttle greater than 70%...). This isn't how real planes behave. DCS world actually models stalls effects via acceleration units.

 

What I did:

 

1.) LUA export correctly handles axis data, so now the G load works regardless of the orientation. The axis mapping and polarity has to be changed for each TFS profile though. See the attached TFS profile for the P-51D.

 

2.) I've tied the RPM effects for the P-51D to the manifold rating instead, so more throttle equals more oomph, through the whole range.

 

3.) Stall effects now work! The script detects minor changes in acceleration units, and creates a speed brake effect to simulate buffeting.

 

Drawbacks:

There are some drawbacks due to the nature of data sets available to LUA exports. The biggest one is that the gears/flaps effects are not tied to the mechanical system, but the cockpit switches. So if the hydraulic system failed and you press the flaps key, the flaps effect will come on even though the flaps are not moving.

 

Attached is a LUA and the P-51D TFS profile. I've made the export.lua to only work with the P-51D and the A-10C. FC3 planes and helicopters will still utilize native IntelliVibe support (I don't fly them much...).

 

Try the attached script/profile, especially for the P-51D. With proper G loading and buffeting effects, flying the P-51D with the TFS3 is a real joy now! At least, in my humble opinion :)

TFS3 Files.zip

Edited July 2, 2013 by recoilfx

[mr_mojo97]

@pgh2atl

Not sure what's happening mate. I emailed Craig and he said they had some issues and were changing suppliers to a New Jersey based company rather than their Foreign manufacturers and they were in the middle of making a new batch. That was about 7 weeks ago and I've heard nothing back either so or sure where they are with orders

[predator-nz]

Hi I put in a order about two months ago and havent heard anything. Hopfully they sort it out soon.

[Cowboy10uk]

Ok, after ordering a number of months ago, I havnt heard a thing, so cancelled that order and reordered, as I had no idea if it had reached the developers.

 

Has anyone heard any update of when we should expect this to be sent out. I appreciate it does seem to be hit and miss.

 

Cowboy10uk

[predator-nz]

Hi I read a post on there web site and they said that was trouble with they production source in the US guess we will have to wait a bit longer.

[Cowboy10uk]

Thanks predator, I guess I'll just wait. I wouldn't mind if they just sent out an email saying thank you for your order. But I've not received anything on either order, or the cancellation. So I've no idea if

 

a. they have received the order

 

Or

 

b. they have cancelled the first one.

 

I was Hoping as the producers have been seen on this forum from time to time. One of them might be able to confirm if they have got the order.

 

It's a fantastic product and certainly they guys on here who have them say it really does work. I just wished the communication was rather better. Actually I just wished there WAS communication.

 

Cowboy10uk

[cichlidfan]

I was Hoping as the producers have been seen on this forum from time to time. One of them might be able to confirm if they have got the order.

 

It's a fantastic product and certainly they guys on here who have them say it really does work. I just wished the communication was rather better. Actually I just wished there WAS communication.

 

 

This is precisely why I have not ordered.