Nnah.., that would be a waste of time.. did you try this step that fourgrinder pointed you to?
- A relatively easy thing you can try is this: Rename your saved games/DCS folder to something like DCS.saveme. Then start DCS and let it create a new file structure. Then load TelemFFB and let it install the export script and modify the export lua. Restart DCS and load into an aircraft and see if the telemetry starts flowing or if you get the same error in the log. All your bindings will be gone since they are stored in DCS folder you renamed, but this is just a test and you can delete the new DCS folder and rename your old one back
Cyep tried that
Cdoes this software prefer windows 10 or 11?
HDo you have any other programs that rely on the export.lua of DCS? Like a buttkicker or winwing peripherals?
NDoesn't care.
After you changed the savegames folder name and let DCS create a new one, did you install any other mods or anything?
Remember you have to restart DCS after the first time you install the export script from TelemFFB. After it exists in export.lua, if TelemFFB were to update the export script in a future update, you only need to start a new flight for it to pick up the updated script.
After you changed the savegames folder name and let DCS create a new one, did you install any other mods or anything?
Remember you have to restart DCS after the first time you install the export script from TelemFFB. After it exists in export.lua, if TelemFFB were to update the export script in a future update, you only need to start a new flight for it to pick up the updated script.
CNope, just launched the sim and picked an instant mission
NMight help if you post a clean copy of the dcs log here when running with the clean save games folder.
- Shut down DCS
- delete the dcs.log in the logs folder.
- Start TelemFFB
- Start DCS
- Start a flight
Cokie dokie
NALERT EDCORE (Main): Can't execute Lua file C:\Users\steve\Saved Games\DCS.PUBLIC\Scripts\Export.lua - no file 'C:\Users\steve\Saved Games\DCS.PUBLIC\Scripts/TelemFFB.lua'What is DCS.PUBLIC ?
Ci have two files, one is public one is for a squadron build
Clittle confused, because there's clearly an export.lua in that folder
Nbut does
The auto install for TelemFFB only looks for
There are two pieces.
C:\Users\steve\Saved Games\DCS.PUBLIC\Scripts/TelemFFB.lua exist?The auto install for TelemFFB only looks for
DCS and DCS.openbeta. If you are running from a save games folder with a different name, you will need to manually place the export script (TelemFFB.lua) in the scripts folder.There are two pieces.
- The entry in export.lua that tells DCS to load the script
- The telemetry script itself (TelemFFB.lua)
Ci'll give that a whirl
CTA DA!!
Cdude, thank you so much
EAh right, every resource I went looking for said to turn FFB on in settings. That'll probably be it
EIt might just be that bug outright, because I turned off FFB in DCS settings and the Phantom just straight up does not detect pedal input at all. I've tried the F/A18, F14, F5, 190A8/D9 and P47 so far and they all naturally detect the Rhino as a pedal.
NThat is strange indeed. If disable FFB globally in DCS, it still recognizes the pedals as a joystick device and they work fine in the phantom.
ESorry I phrased that poorly, I mean the Phantom doesn't recognise the Rhino input at all under any circumstance for me.
Turning on/off FFB settings just fixes the main pitching issue.
Turning on/off FFB settings just fixes the main pitching issue.
CJust assembled ffb pedals and having motor voltage faults when moving the pedals. It turns the motor off then on. Does anyone have this experience and any trouble shooting ideas? I am sure it's something I did, but at a loss figuring it out.
CThink I have it all fixed. Appears to be a faulty power supply. Salvaged an old one I had and after some testing seems to work fine now.
KUse another psu. I had the same effect with a notebook psu. Now I'm using a Meanwell without any problems.
HYou need to plug in two USB-connectors in the Rhino-Crosswinds. One for the toe-brakes and one for the actual FFB-board. But you can only bind the axis with the FFB-device. You MUST clear the rudder-axis of the original Crosswinds.
Eits clear
EI've got the Virpil pedals, but its the same concept, I haven't put a cable directly into the pedals yet
P@walmis Hey m8, sorry for the ping. I got my new style cable today is there anything I need to know about swapping this out? I'm guessing I open up the side panel to gain access to the inside?
WHi, not the side panel - the rear panel (where the fan is). You will probably need to to cut the old cable and pass through the new one
PI have a new cnc bit to go on so would I be able to just unplug the old cable & remove it all? Or do you mean even replacing that I'd have to cut the cable? Rear panel yes that's right 
WYes, to remove the old cable you will have to cut it (or unsolder it). The new one with the small connector will fit through the gimbal.
Pahh I understand thanks for the help as always.
AOpen question: is there any potential for either the Rhino software or the TelemFFB to cause a CTD for the other person in a multi crew module?
WYou mean on the other end of a network cable? No chance
AI’ve played CP/G in the Kiowa in DCS a couple of times now, and with different people in the pilot seat. Every single time, the game has crashed on the pilot’s end.
Other people in the group have played the Kiowa without experiencing this, and AFAIK no one else has a Rhino.
It’s a long shot and likely caused by the Kiowa just being unstable, but just gotta ask
Other people in the group have played the Kiowa without experiencing this, and AFAIK no one else has a Rhino.
It’s a long shot and likely caused by the Kiowa just being unstable, but just gotta ask
AAight, it did seem far fetched, but had to ask just to rule it out
TI assume you’ve mapped pilot’s commands, as well as co-pilot’s? It’s not supposed to let those commands go through if someone is in the other seat, but maybe it is and that’s breaking something? Only flown SP in the Kiowa so far but it’s fun!
OJust finished installing my Rhino, running cables, etc. I noticed that it runs pretty well in DCS just with FFB checked. What do people tend to run for default/basic settings in Rhino configurator?
Bhow do i roll back the firmware, it broke my rhino
Awhat broke? (not sure how to roll back, tbh)
Bi think the issue was i chose to update the firmware before updating ffb configurator, seems fixed now
Bthanks!
Aword, glad you got it sorted -- but yeah -- i assume once you've flashed the firmware, you will require the new configurator software or else it probably won't know how to talk to the rhino
OJust tried the new beta firmware and the fan control is a godsend for my ears 
Question though - any advice on fan settings to use or avoid? Can we raise the fan start temperature to 40 or 45 or not recommended? Is 25% starting fan ok or again not recommended.
Just some general parameters that the motor should be operating under would be helpful to understand whats ok and not ok with the fan control (I'm pretty sure I didn't see this in the change log - apologies if its there).
And thanks again for implementing this! I personally feel its a really nice QoL upgrade as the fan was very loud before and now its much much quieter (even if it runs for longer now).
Question though - any advice on fan settings to use or avoid? Can we raise the fan start temperature to 40 or 45 or not recommended? Is 25% starting fan ok or again not recommended.
Just some general parameters that the motor should be operating under would be helpful to understand whats ok and not ok with the fan control (I'm pretty sure I didn't see this in the change log - apologies if its there).
And thanks again for implementing this! I personally feel its a really nice QoL upgrade as the fan was very loud before and now its much much quieter (even if it runs for longer now).
HThe earlier and the more you cool the better. If you NEED all the cooling depends a lot on what you do. When you just fly helicopters you won't need much cooling. When you do a lot of high-G dogfighting (in an F-16 e.g.) You want all the cooling all the time if you ask me.
HThe problem is, that the temperature that is actually measured is the one of the motor-driver. The motor themselves serve as giant heatsinks. Which is nice for short temp-spikes of the drivers because they cool down again very quickly. Once the motors themselves are heated up though..... A continuous light cooling would be best in my opinion, so that they don't heat up that much in the first place.
OThanks. I'll start the fans from an early temp then (maybe 35) but at a lower speed so that there's at least constant airflow 
HI think that's reasonable. My plan as well. Just have them running constantly but almost inaudible and have them ramp up at their usual treshold (50 C I think).
HJust help to cool down the thermal mass a little all the time.
RSomething went off, I've got joystick and pedal going on but only one of the board can be connected after the firmware update. Any way to fix this? I checked the PID is unique to each joystick(2055) and pedal(2052).
RI should have said ''one at a time'. The second one gets detected as USB as beep goes, but it gets ignored on configurator, then USB gets disconnected on second board after a while.
