PeterP

.

Click- and Customizable Radio Menu for DCS World

the forum search is your friend ! ;) >>> HUD-only view

Thank you for sharing you progress ! Don't worry ;) - If it feels 'right' , you are on the right track and you can finish the 'cosmetics' later. My 'first attempt' looked very similar to yours. :)

:thumbup: Thank you for thanking me - Glad you figured it out! :) ...I have running 8 different controllers myself with a unique profile for almost each plane... , ... I know that it can be sometimes a pain and 'time-vampire' to find the culprit after each update/patch ... ;)

Rebuild the default 1.2.6 A-10C key-bindings profile. A 'How-To' can be found here: Sticky: corrupt calibration? crazy joystick response? Use this tools Fix it:

That's a indication for a broken script with a invalid syntax. Please check your *.lua for typos.

>>> Total mystery with this mission file

No, there is no need for guessing. You can change your eye-position while the simulation is running.

» Dummies Guide for the “MonitorSetup.lua“

Thank you for thanking me.

Thank you for thanking me. This may help you in your progress to master the "frogfoot" : KNEEBOARD Tablet Mod for DCS World and/or Keyboard controls for the Su-25T listed inside the Kneeboard

...sorry, my Spanish is terrible... Read, think, try, re-think... , try again and understand: » Dummies Guide for the “MonitorSetup.lua“

... it will be fixed in the next major update. ... Have a look to get a idea what you are missing: (following vids are made with highly modified MSSFFB2 hardware, but it applies the same to a "standard" FFB stick - follow the video info at youube to see why I have uploaded them and for more info) FFB in the Ka-50 (same applies to the Huey) : FFB in the A-10 : FFB in the P-51D : - sorry , no 1:1 comparsion vid - but look at the Virtual-stick and the control-indicator to see what the real FFB stick does wile getting nearer to a stall: A highly variable stick-shaking before reaching a stall, also a limb stick when no airflow and getting stiffer as you going faster. A absulute unique helper to fly the P-51D at the 'edge'. ...and you also feel your set trim in the P-51D (as in all other DCS modules also)as the trim input will deflect your stick. What has been shown/named above is similar in all FC3 planes Well, the Trim behaviour is up to now(1.2.4) a little bugged for the G940 (not going limb when trimmer is pressed down) - so please have also a look at this thread: >>> G940 Trim Workaround My conclusion: Using a flight-Sim without a proper FFB stick is like having XXX with a Rubber-doll - it just doesn't feels right.

As others already said - It's not really hard to build your own without the limitations (lack of buttons) that the high-price ready-to-use solutions have: KA-50 collective: another picture-tale - a 5 days building diary. >>>

>>>

follow the links in this post: Sticky: Dummies Guide for the “MonitorSetup.lua“

. Sorry , don't have time to explain in detail how to set up a new image path for each module. Please just compare my Moded files with the default and you will see/learn how to set up different image content for each plane/module. Files of interest: \DCS World\Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\indicator\init.lua local aircraft = get_aircraft_type() or "" if aircraft == 'A-10A' or aircraft == 'A-10C' or aircraft == 'F-15C' or aircraft == 'Ka-50' or aircraft == 'Mi-8MT' or aircraft == 'MiG-29A' or aircraft == 'MiG-29G' or aircraft == 'MiG-29S' or aircraft == 'P-51D' or aircraft == 'Su-25' or aircraft == 'Su-25T' or aircraft == 'Su-27' or aircraft == 'Su-33' or aircraft == 'UH-1H' then dofile(LockOn_Options.common_script_path.."KNEEBOARD/indicator/init_KNEEBOARD_BASE_MOD.lua") else dofile(LockOn_Options.common_script_path.."KNEEBOARD/indicator/init_DEFAULT.lua") end \DCS World\Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\indicator\init_KNEEBOARD_BASE_MOD.lua starting line #132: if aircraft == 'A-10A' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/A-10A") elseif aircraft == 'A-10C' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/A-10C") elseif aircraft == 'F-15C' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/F-15C") elseif aircraft == 'Ka-50' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/Ka-50") elseif aircraft == 'Mi-8MT' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/Mi-8MTV2") elseif aircraft == 'MiG-29A' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/MiG-29A") elseif aircraft == 'MiG-29G' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/MiG-29G") elseif aircraft == 'MiG-29S' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/MiG-29S") elseif aircraft == 'P-51D' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/P-51D") elseif aircraft == 'Su-25' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/Su-25") elseif aircraft == 'Su-25T' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/Su-25T") elseif aircraft == 'Su-27' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/Su-27") elseif aircraft == 'Su-33' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/Su-33") elseif aircraft == 'UH-1H' then scan_path("KNEEBOARD_MOD_PeterP/Custom_Charts/UH-1H") end scan_path(LockOn_Options.common_script_path.."KNEEBOARD/indicator/Common_Charts") scan_path(get_terrain_related_data("KNEEBOARD")) scan_path(lfs.writedir().."KNEEBOARD")

...so please change your default FOV to your liking: Another instruction:

KNEEBOARD Export for 'multimonitorsetup.lua' in all modules - DCS 1.2.4

Sorry that I'm not able to answer everything how I self would like to ... I have quit my old daily job and I'm in the progress to start something new... This and my family takes my whole attention. I will be back soon... I kindly ask the more experienced users to help others out (like you already do). "reset" your inputs if something isn't working . Follow this link and extract the needed info yourself how to do it: corrupt calibration? crazy joystick response? Use this tools to Fix it:

Happy Birthday ! Many, many, many more to come - enjoy your self with your family and mates. Thanks for all your continuous updates and everything !

See it this way: You probably deal with a company that usually works only with professionals and/or customers that buy a whole solution including maintain contracts for a whole life-cycle for their product. And normally their deals are much more worth than 25,000 before they even start to communicate with a costumer at all... They probably know that you got it "second-hand" and you are probably not the first that asked for assistance . I bet they just call out the 25,000 price tag just as a 'entrance fee' - so that the needed time that their engineers use to communicate with you is paid - and this will also hold off all others hobbyists that have similar requests. It's all about money - they didn't founded their company just to make people happy. And I bet you would do it the same when you would run a multi-million dollar company that has to calculate very sharp to withstand against other competitors and has to protect its intellectual properties. :) But moving a servo is no witchery and all possible problems are already well described and there are open-source solutions available for it already. My best guess to find the answers you are looking for would to open a thread with a detailed explanation in the XSimulator.net community. Its the #1 source for DIY Motion Simulators, and many professionals share their knowledge also on this forum. There is a tool called "Yoda" that analyses FFB commands and can translate this data to drive any motor you can hook up. I think this would be the most elegant solution. And you should really find contact to an mechatronics engineer that is able to really tell you what motors you got there.

Yes, sure. so please look up if your sim assignment matches your game-mode assignment. This may help: corrupt calibration? crazy joystick response? Use this tools Fix it: ...and please don't forget to read at least the Mi-8 Quickstart manual.

..and crashed the Cobra. *EXTENDED* Helicopter Crash Caught On Camera (subtitled) - Top ...