majapahit

your width = 1920 should be / have been width = 3 x 1920 ?

OK good news, I'll dust off that keypad I still have lying around ..

your first column needs to be the actual original ASCII or keycode (listed on the wiki page or web page somewhere), then substitute keycode, then your comment like for a numpad (and set your numlock properly) HID\VID_05C7&PID_7001&REV_0003&MI_00 Keypad GREY remapper enter a comment with a space at the start of the line like this Num/ C-F weapon mode Rotate LEFT Num* A-F weapon mode Rotate RIGHT BS RESET button Num7 Z Num8 H Num9 H Num- Z Num4 Q Num5 Q AUTO TURN Num6 A-S HEADON A-A Num+ rS-O Laser standby -OFF ... remapper doesn't seem to work under Win 10 though, works under Win 7

2.5 is also bloody slow on multiple screens, 1.5.8 is 2x faster Annoying.

makes for 5760x2130 Viewports = { Center = { x = 0; y = 0; width = 5760; height = 2130; viewDx = 0; viewDy = 0; aspect = 5760/2130; } } GUI_center= { x = 1920; y = 0; width = 1920; height = 1080 ; } UIMainView = GUI_center name this in the file field, save as file, select in options you place the bottom screen via Windows display or NVidia Control Panel etc. that's it for 1 big viewport

1.5.8 now works great (mine) 2.5 crashes with 4x multimonitor setup in T, multimonitor labels issue still there, did I mention CRASHES but not in NVidia 3x monitor surround mode, FULL 1 SCREEN 5760x1080, correct labels, no crashing, high FPS. help, I really like my 4th touchscreen to show instruments, not running full screen, FPS OK, WHICH WORKS IN 1.5.8

indeed, broken in win10 I pm'ed the github author, maybe he reacts

I find them too big, no room on my desk, have 4 screens and 2x HOTAS already there, these keypads are small

yep run the .bat in a DOS-box, it will show you the definitions of the config_file

run.bat: remapper DCS.txt (where DCS.txt is the config files) in Windows 10 there are/I had problems with security in my start menu directory tree (none in Windows 7) I have/had trouble in my start menu with copies of the .bat files. with for instance: run.bat: "i:\TEKST\My Games\DCS\Remapper\remapper.exe" DCS.txt so, I had to create in my start menu, link files .lnk that in the advanced options have 'run as administrator' checked. then again one can always go the the directory of the .exe file and start from there (I have batch files that unload all of the utility files for my flightsims, that took a while before I found out why killing the programs didn't work anymore under Windows 10)

Some short hints. - Download the .zip - read the download page CAREFULLY (over and over) <<----- .. you need to find the hardware ID for your <second keyboard> = Numpad. Bla bla bla that has an ENTER key > you run a CMD window in the remapper.exe directory so Win can find remapper.exe (or add path) > you type in the command line <remapper.exe> > DO NOT hit ENTER on your main keyboard > hit the ENTER key on the numboard > this will generate an ID on the screen > copy paste the ID into a notepad > you need this ID as the VERY FISRT LINE of your command config file, let’s say <DCS.TXT> >>>> in DCS you need to ADD simple key commands to the definitions config, for remapper CAN NOT distinguish between double shift keys (or, I think the Window) -Keys > you find the code for the keys of the Numpad by reading the text CAREFULLY, > you add or checked simple keystrokes for the commands > you write this out in the config.file that has the ID as first line > you run remapper.exe <config.file> as the command line, et voila. 1 of my config.files, in this case DCS.TXT (I can use 2 Numpads for the 2 MFCD’s of the A10C): (start) HID\VID_1710&PID_5612&REV_0100 <space>Keypad Black remapper / enter a comment with a space at the start of the line like this, "NUM" are the keys of the Numpad, <NUMKEY>space<KEY COMMAND>space<YOUR OWN DESCRIPTION // Num/ rS-2 ROSB2 TGP A-G Num* rS-4 ROSB4 TGP A-A Num- U Coolie Up HUD SOI Num7 S-1 FLT PLAN Num8 S-2 MARK Num9 S-3 MISSION Num+ U Coolie Up HUD SOI Num4 A-5 LOSB15 TAD Num5 A-4 LOSB14 DSMS Num6 A-3 LOSB13 TGP-L Num1 rA-5 ROSB15 TGP-R Num2 rA-4 ROSB14 MAV Num3 rA-3 ROSB14 CDU Num0 A-3 LOSB13 TGP-L Num. A-4 LOSB14 DSMS (END) that’s it

That's an amazing reply, bit dumb, for it works here. Are you able to read ?

http://www.2112design.com/blog/multi-keyboard-remapper/

(go annoy yourself somewhere else thank you)

With a multimonitor setup (4x in T) I used the forum ‘recommended’ hack of MSAA set to Off and setting AA and FXAA through the Nvidia Inspector panel, that worked, no 7 FPS but a wholesome steady 35-45 FPS (with DS On for not-the-ugly-trees). I noticed plenty of posts mentioning ‘doesn’t work here’, by they would be doing something wrong, right? Well not any more. Doesn’t work anymore all of a sudden, all Nvidia Inspector/Control panel setting stopped working, horrible non-AA graphics, only in-game settings work, which is either horrible or 7FPS. ?

MUSTANG those 2.5 trees are boring ..... !!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! !

One of the 1.5 default missions has trucks now hiding in a piece of forest (they're moved couple of hundred yards in the 2.5 provided - same - missions). But I can - still - hit these by blindly spraying cannon fire approximately at the TGP designator, can even search, lock on and destroy with MK-D or blindly area lock with MK-H and have kills. Wonderful ...

I'm alternating between separate installs of 1.5.8 and 2.5, and I notice I like DCS 1.5.8 better. DCS 1.5.8 appears to be the perfect (short life span perfect) 1.5.x. Everything actually works (labels, trees, beautiful Mustang map) and my FPS is over 100 (105-125) instead of 35 (with NVidia Inspector AA settings).

I use NVidia's special AA in Nvidia Inspector 'Antialsiasing' dropdown', SUPERVCAA 64X 4v 12 best performance/quality AA trade-off, even a bit better than NVidia's 16x CSAA 2cts

prob because you're using multiple monitors ... the bug is back DCS 'fixed' this in 1.5.8 (was introduced in 1.5.6 or something), oops

Updated, freeze/crash after 6min30 (I run multiscreen / labels don't work)

You can assigns screen areas for MFCD output like LEFT_MFCD = { x = 1920-10-1600*0.75; y = 1080-10-1000*0.75; width = 1600*0.75; height = 1000*0.75; } RIGHT_MFCD = { x = 3840+10; y = 1080-10-400*2; width = 400*1.72; height = 400*2; } You will render the sum of the assigned pixel area, so assign with some thought, above is 2 MFCD on 4x 1080p monitor T-setup with MFCD on the left and right monitor in the bottom of the screen adjacent to the center monitor you will want your 2 MFCD definition on a right hand side or underneath, whatever needs the smallest render area my 2 cts

in your <MonitorSetup>.lua don't define 3 viewports but 1 spanning the total pix then the perspective will be the same over all.

same problem here 4 monitors T-setup multi monitor labels problem was fixed in 1.5.7 to 1.5.8 Now we can start over, what bummer ..

same problem here 4 monitors T-setup multi monitor labels problem was fixed in 1.5.7 to 1.5.8 Now we can start over, what bummer ..