OziasMidwinter

I had a similar problem with a TM Cougar TQS when used with a USB hub. I Also ran an arduino LED clock off the same hub, with the clock plugged in the Windows game controller would not detect the TQS, but with the clock disconnected the TQS was detected. I'm guessing that the clock was drawing a fair bit of power from the hub and it was preventing the TQS USB interface working correctly, either that or windows didn't liked having multiple micro-controller devices on the same hub (the TQS has been modified with a arduino micro-controller to turn it into a standalone USB device instead of connecting through the Cougar joystick.) I'd trying disconnecting any other devices from the hub, or try connecting the CM3 directly to the PC

Hello rel4y I would be interested in acquiring a couple of replacement TQS radar cursor microsticks if you have any available.

I've got a lua script set up to display the main viewport on one monitor, and two MFDs (and apache TEDAC) on a second monitor. I use the same script in the apache, Ka-50, F-16 and F/A-18 the MFDs all appear in the monitor in the correct place. When I switch to the AV8B harrier, the MFD displays do not show up in the F1 cockpit view, but do display when I switch to the F2 external view, and disappear when I switch back to the F1 view. The script uses the generic LEFT_MFCD and RIGHT_MFCD identifiers as they seem to work in the modules listed above. _ = function(p) return p; end; name = _('AH-64D Apache CPG Dual Monitor: m1 - Viewport, m2 - MFDs, TEDAC (equal)'); Description = 'dual monitor: viewport on main 2560 x 1080 (21:9 aspect ratio), MFDs and TEDAC on second monitor: 1680 x 1050 (16/10 aspect ratio) bottom aligned' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1080; viewDx = 0; viewDy = 0; aspect = 21/9; } } LEFT_MFCD = { x = 2560; y = 30; width = 554; height = 554; } RIGHT_MFCD = { x = 3668; y = 30; width = 554; height = 554; } TEDAC = { x = 3114; y = 30; width = 554; height = 554; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Is it a case of using specific IDs for the AV8b displays instead of the generic IDs, or is just a weird bug with the harrier?

(pre-production) AUO 23.6″ circular LCD panel (model P236RVN01.0) https://www.digitalview.com/blog/23-6-circular-lcd-panel/ The 5" panel might be useful for 50's-70's era radar displays

That would be Megan's Little Helper No! Not The Bees! My Face! My Face! (how to turn a serious 70's mystery/horror film into a comedy)

Just for variety when I run this training mission it freezes on the flap operation check

6 minute youtube vid showing the Ka-50 HUD: [ame=https://www.youtube.com/watch?v=_6_dFUcZiJY]ka-50 view through HUD[/ame]