icemaker

Thanks a lot!

Good news mate ! Any news on rwr and other a10c stuff?

G00dnight. Have you tested. Tv maverick not IR?

Cool ! Noticed something: tv mavericks rare Also In color. Is that realistic ?

@G00dnight i don't have the Sabre and i have made some tests and the problem is form uMFCD side.

I noticend another strange behaviour: uMFCD changes size when i activate/deactivate mirrors, between medium and large.

i export data to my home cokpit, and when i use uMFCD i have an LUA error related to my export.lua but only when using uMFCD. And here you have my export.lua The error seems to be between LuaExportbeforeNextFrame and LuaExportAfterNextFrame.

Ok for me if i can give any help.

It's not iceman but IceMakeR :D But Sgt_Baker has already far beated what i have done in EMC even for a beta:notworthy:

Hy Sgt_Baker, works mostly fine, very great job i gained around 15/20 FPS :thumbup: more than i could ever dream! :joystick: Here are my current problems: -Exports not working when using uMFCD -Mouse floats and stills moving for a fiew seconds after i stop moving it. -Can't save Exports positions -The touch MFCDs option seems not working, the MFCD still touch sensitive even the option is unchecked.

will uMFCD export all the other viewports like Radio frequencies and CMSC/CMSP? And could it run in a second computer for rendering and maybe decrease the Sim Computer load?

Thanks mate! Works fine! Do you think it could be possible to create a datacard with all infos from mission like loadout and airbase data, expected air defenses and so on?

I use ED provided Missions : Shooting gallery and defend camp yankee

Hello, My dynamic kneeboard only works in MP not in Single Player missions. don't know Why, i had this error in DCS.log, i think it searches for TMP/.miz file but this file is only for MP missions.

Got same problem here with missiondata.lua both with new and old missions. got this on my DCS Log

Read first and #8 posts where all is explained. You need to wire, for example, pin 26 to pin 38 to use a push button, and you don't need resistors but an 1n4148 Diode to avoid ghosting problems.

just a little drilling to ensure the most glue surface contact. For the glue i used cyanolite with catalyst

just buy a Gamepad mini stick replacement like this : Cut the base and paste it over the slew mini-stick, change game axis sensibility and it's done!

Litlle update: Some Cockpit pictures with lights on Picture of my Cockpit view The panel Hydraulic Fuel finished (Almost...) And a little Warthog Mod for a better slew look and precision.

This is a bug since ED changed Registry keys where the path to DCS was previously stored. Search in this thread someone has already answered this kind of problem. I'll try to take some time to update EMC to add manual path configuration, but i can't say when. As soon as possible.

Some WIP pictures of my front Console.

Due to the last update all values should be +1 tu get correct data so for CMSP use list_indication(8 ) and so on

I have been looking in LUA to see if dealing with this switch position initialization is possible, like for the Warthog HOTAS. It seems that it's a function inside the input.dll that manages that but is only available for "official" hotas so impossible to use it with our hown home-made devices. Maybe whe should ask ED to open this function to other devices.

Ok understood, i don't criticize i just ask a question, i'm a totally noob concerning all that microcontroller stuff! The limitation to 32 or 64 is a concern with devices like the CDU using 67 buttons alone, which means two cards for the same Peripheral, with a board that can mangage that huge amount of buttons is that i only need 1 board to make my CDU (i can also placemy board into the same enclosure) ofcourse i'll probably never use 256 buttons for the same device but i have enough room to create the biggest device with only one board. Anyway i think your work is very interesting and opens more rooms for guys like me that create home cockpits, and i'll follow your project with massive attention! Looking forward to read it! :thumbup:

Interesting project! Do you plan to make it compatible with ATMEGA16U2 Chips like in ATMEGA 2560 boards? I dont understand the 32 buttons limitation you have. I actually use ATMEGA Boards where i can wire up to 256 buttons (2x 128 Buttons Joysticks) and it works smooth on DCS.