hannibal

i have uninstalled Simhub. and u also reinstalled Simshaker i can NOT get telemetry so that effects run on simshaker.. i see the verbose log is showing good activity on Aviators, how ever NOTHING is happening in sound module. (yes correct sound card is select, and test works) looked at my log file but not helping... repaired the export lua, with no success my export lua contains local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') dofile(SimShakerlfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil) dofile(lfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]]) log.log

would appreicate anything that is agile and has anti tank capability , plus sensors that can store target location...and A-A capability. i love the apache, just wish it was more agile! much need fast & pew pew heli needed!

i had yaw 1... if i recall, there was an yaw emulator application, so u can visually see telemetry behavior without having to run the physical yaw chair... to help you see oscillations with out having to take a chance in damaging your hardware @Bojanglez

i just loaded all the carriers in one file.. so same conditions what kind of rig do u have and what software to u pull telemetry from? @Bojanglez

on the surge side of things for lincoln and washington, it seem fine to me. i didnt get the continuing spikes of telemetry when the tomcat was hooking up. the carriers that had the continuing spikes basically shook the motion platform violently. in my demo video, i was in the washington, i shot off the cat no major problems. when i went back to tune my profile, when i tried to catapult off the roosevelt, my motion platform was shaking violently, even disconnecting usb ports from my joysticks so this past weekend i had some time to tune. so above post was the result of my findings. i also had to configure my profile with filters on surge (originally my filters were for sway, since from beginning, i always have a violent studder when starting to move the tomcat and needed spike filters to minimize the studder) if you are a mover user, i found that using MALP nested in EMALP does a descent job to minimize the Surge oscillations, and still get catapult effect (at least via graphic viewer), i hope to test out my profile next time around on the platform.

my origins of playing endless hours on battlefield 2, particularly most of it flying the super cobra.. i definitely a huge fan of super cobra...

As a motion platform enthusiast, i have a hexapod powered by FlyPT Mover to read data from DCS I find Mover easier to work with an customizable so that i am able to make profiles for any DCS aircraft, each DCS aircraft which seemingly has its own characteristics. unfortunately Mover is outdated, and not all telemetry is utilized, especially Stall State and RPM after investigation and trial and error to understand the lua functions, i was able to get RPM data and send it to Canopy data input that mover has hardcoded. By swapping Stall% for RPM%, in the lua hook file, i now am able to do something with RPM.. which now allows me to make motion by RPM. (RPM% more use full than Stall%) it is finally nice to throttle up, and have the telemetry shake up the platform as if i am powering up high power jet engines!! Hannibal Su25T with RPM.zip

Testing today. flew F14 module to hookup to all aircraft carriers. findings for the SURGE telemetry 1) Forrestal did not have wild oscillations for surge, did observe one large spike for surge. 2) Washington did not have wild oscillations for surge 3) Lincoln did not have wild oscillations for surge 4) Truman has wild oscillations during hookup 5) Stennis has oscillations but (not wild) during hookup 6) Roosevelt has wild oscillations during hookup if someone else like to test/investigate motion relative to aircraft carriers, would help to try to find root cause... @BrassEm @Bojanglez

hello @=Andre= @f4l0 im currently having an issue with simshaker. i believe my problem is because i have SimHub installed, which also has a script/hook lua file for bass shakers. at the moment, simhub will take telemetry from dcs to my audio card but simshaker does not, even though test the module in sound module works with my audio card.. im also going to ask the simhub group, but im checking here also, any info much appreciated

https://wiki.hoggitworld.com/view/DCS_Export_Script

trying to figure out dcs telemetry by investigating data in and out, would like to just see the contents of the LoGetMCPState() in a command prompt, if not a textfile.. any suggestions, much appreciated. resources https://forum.dcs.world/topic/100222-tutorial-introduction-to-lua-scripting/ http://lua-users.org/wiki/LuaDirectory https://wiki.hoggitworld.com/view/DCS_export

the gazelle is awesome. i love this bird. the only thing i would like to see fix is the minigun slew range when mapped to a joystick. its a downer to use a joystick, and i can not point the minigun towards the front of the aircraft, the slew range is unusable when flying on the move. video here shows that when joystick reaches full deflection, the corresponding in game slew has a quarter of the range. PLEASE FIX TO ALLOW MINIGUN TO POINT TO FRONT OF THE AIRCRAFT WITH A JOYSTICK! (also the up/down slew, in addition to the left/right slew) pretty please @Polychop Simulations

@BrassEm if u have time to checkout telemetry catapults on all carriers, maybe we can narrow down something? i will also try to do when i have a chance

ok, plot thickens. jumped on F14 and had wild oscillations. todays testing tuning had me experience the wild oscillations (on surge output data) on both F18 and F14 on the CVN 72 roosevelt (my f14 video that had no issue was on CVN 73) so that is where i find my self with my current findings....

ok.. further investigation with F18... just like @BrassEm's findings with chart, i can also see on my telemetry viewer via flyPT mover, the outrageous telemetry happens on the Surge data for the F18C upon catapult hookup.

please dont mind me @BIGNEWY i know u have mention to devs about this issue.. but i am just writing this comment to share my experience. these past two days i been doing some tuning, tweaking my motion profile for F14. today i decide to give my profile a try for the F18, and during catapult hookup, the telemetry was extreme for the hornet! it even shift my motion platform off the mat that i have it on! was hoping that tomcat telemetry would be similar to hornet, but it is not (as the case with every other dcs aircraft) but in order to get a good experience it is necessary to tune for each aircraft, no one size fits all, just like how simshaker is for audio.. i hope to tweak a profile tweak a profile for F18. but sharing that something weird in the catapult hookup, and its different between F18 and F14.

so i use Andre's simshaker. i check startup and shutdown for the AH64D, and everything works ok. how ever andre's simshaker dont use RPM telemetry for AH64D. today i spend the afternoon tuning my motion platform to include RPM for some planes, had time to configure the F14 and P51, each with its specific profile on my motion platoform. there is some lua programming for LoGetEngineInfo which includes the RPM left engine and right engine. later ill see what value a helicopter gives me. at this moment, i think its on buttkicker to configure their Hapticonnect software correcly, and from my experience, each aircraft has to be tuned... so if hapticonnect is using a general function to handle ALL aircraft, the effects will be BAD. (from google search my impression is that hapticonnect does not include profiles for each aircraft, but i dont know, cause i DO NOT have this software) at this time, my opinion is go andre's simeshaker or simHAptic

Hey everyone. Buttkicker, dayton audio pucks and aura shakers are hardware, not software. So first question. What software are u using? It's going to be Andres simshaker or buttkicker hapticonnect, or simHaptic by rk Apps.. Which one are u using @Pribs86

after some investigation, i see that the stall is formulated from the Export.LoGetMCPState() function with a data structure in boolean states 1 for true, 0 for false. in the mover lua file is the script local alarm = Export.LoGetMCPState() --[[ returned table keys for LoGetMCPState(): "LeftEngineFailure" "RightEngineFailure" "HydraulicsFailure" "ACSFailure" "AutopilotFailure" "AutopilotOn" "MasterWarning" "LeftTailPlaneFailure" "RightTailPlaneFailure" "LeftAileronFailure" "RightAileronFailure" "CanopyOpen" "CannonFailure" "StallSignalization" "LeftMainPumpFailure" "RightMainPumpFailure" "LeftWingPumpFailure" "RightWingPumpFailure" "RadarFailure" "EOSFailure" "MLWSFailure" "RWSFailure" "ECMFailure" "GearFailure" "MFDFailure" "HUDFailure" "HelmetFailure" "FuelTankDamage" ]]-- local stall = 0 for k,v in pairs(alarm) do if k == "StallSignalization" then if v == true then stall = 1 end end end after trying "CanopyOpen" as a test, i can see states change in the game when i open close the canopy. how ever results from the "StallSignalization" does not change.. and seems to stay in a false state.. any advice?

how does one check SMS settings?

no problem!

@BrassEm what kind of rig are you running?

hexapod motion platform user here. i use the flyPT mover software to read the DCS telemetry. for the longest time i have not see any data for the STALL parameter and i have not seen it work. flyPT mover uses a lua file / script as a hook inspecting the lua file, data is in a function called DCSClient:send with the following program socket.try(DCSClient:send( -- 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 string.format("%.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f %.4f", acceleration.x, -- 00 = Lateral acceleration (G) acceleration.z, -- 01 = Lateral acceleration (G) acceleration.y, -- 02 = Vertical acceleration (G) speed.x, -- 03 = Lateral speed (m/s) speed.z, -- 04 = Longitudinal speed (m/s) speed.y, -- 05 = Vertical speed (m/s) rotationSpeed.y, -- 06 = Rotation speed around y (yaw in rad/s) rotationSpeed.x, -- 07 = Rotation speed around x (roll in rad/s) rotationSpeed.z, -- 08 = Rotation speed around z (pitch in rad/s) o.Heading, -- 09 = Yaw position (rad) o.Bank, -- 10 = Roll position (rad) o.Pitch, -- 11 = Pitch position (rad) Export.LoGetTrueAirSpeed(), -- 12 = Air speed (m/s) Export.LoGetAircraftDrawArgumentValue(1), -- 13 = Front/Rear landing gear (0 to 1)? Export.LoGetAircraftDrawArgumentValue(2), -- 14 = Turning landing gear (0 to 1)? Export.LoGetAircraftDrawArgumentValue(4), -- 15 = Left landing gear (0 to 1)? Export.LoGetAircraftDrawArgumentValue(6), -- 16 = Right landing gear (0 to 1)? Export.LoGetAltitudeAboveGroundLevel(), -- 17 = Vertical position relative to ground (m) mechInfo.flaps.value, -- 18 = Flaps amount (%) mechInfo.gear.value, -- 19 = Delployed landing gear (%) mechInfo.speedbrakes.value, -- 20 = Speed brakes (%) mechInfo.canopy.value, -- 21 = Canopy open (%) stall, -- 22 = Stall alarm (0 or 1) Export.LoGetAngleOfAttack(), -- 23 = Angle of attack Export.LoGetModelTime() -- 24 = Time in seconds ))) i notice that the is something wrong with the Stall variable if someone out there that knows lua export variables... please share what the correct variable name is, and if it is in the correct position in the data structure array.... would appreciate!

Tuning a motion platform is not easy. Dcs is even harder considering each aircraft has its own behaviors. Plus one person's tuning preference may not be someone else preference We have what we have and I make the best that I can given the situation, and showing that, if anyone just wanted to get their expensive rigs to work on dcs..else u are at the mercy of ED team to correct the erroneous telemetry. Generally I don't need tons of motion for a great experience. I've tuned my setup to my liking, and I feel I have a good motion fidelity. But I agree that there are erroneous telemetry on the carrier that should not be there.