minimi66

Hi guys, has anyone who is using the CUBESIM USB LCD screens for MFD/DDI purposes had a problem where the on-screen output is reversed from 3 o clock to 9 oclock as seen in the attached image? I have 3 of them and its happened on one of them as of last night? The other 2 are fine. Tried all the usual un-plugging, re-starting PC etc etc. malarkey but no joy fixing it? Have messaged Cube Sim on FB but no answer yet. Probably the time difference from UK. Also went into the actual LCD screen setup options via the buttons on the right side of the back box but resetting or autoconfig from there didn't fix it unfortunately? Can't change anything via nVidia Control Panel as the screens are USB, nothing in Windows 10 Display Settings fixes it either? Any ideas or help most appreciated? Thanks.

Ah, that's cool! Thanks very much for the info! Have a good one! Hi, Yes it does, so i am pretty happy that all is good!! The _downloads folder is there and growing steadily as the morning goes on! So i think i'm golden! Thanks for the response.

I've got pretty crap broadband where i live and was wondering if i had to stop the updater and then re-start it later (say night hours 12:00-06:00) when it tends to be faster, will it pick up from where i stopped it or re-start from the beginning? I've never tested this to find out, am trying to d/l 2.7 currently. 47 GB.... I am erring on the side of thinking this probably isn't possible..... Thanks.

Had my Warthog HOTAS since Oct 2011, it has never let me down in any way. Tiny amount of movement (1-2mm if that?) in the throttle but never notice it when flying. I now have the F/A-18C Add on Grip too, that too is a great piece of kit, only complaint is the SCS can be a bit "sticky" at times. Personally i want the authenticity of the TM products in that they are physically pretty much identical to their real world counterparts. I still wouldn't trade my setup right now for any other manufacturer. The only thing i wish is that i'd never sold my TM Cougar years ago!! Especially now they can be modded to USB and work seamlessly with DCS. Been trying to get the Cougar throttle on eBay as recently as last week but got outbid! Will keep trying. Just my 2 cents..... Happy Easter folks!

@Dauntless Yes, opening the .miz file in 7zip and altering the monitor setup values in the options fixed it straight away. The file wasn't reflecting my correct desktop resolution/aspect ratio or the special monitorsetup config file i have to enable the 3 Cubesim MFD's. It works fine now, thanks for the info.

@Dauntless Thanks i'll check that out!

Thanks for the tips guys, i checked those things you mentioned but the answer was actually very simple! I had only tried the IA mission called Close Air Support with the Viper. The bug seems to exist only on that mission, all other Viper missions work fine just the way they should. So there's something amiss with that mission, at least on my system anyway? I wonder if anyone else has experienced it? Thanks.

I have just installed the Stable version for the first time and the Viper (along with a few other modules). I have a 4 screen setup with a 3440 x 1440 monitor and 3 x Cubesim 800 x 600 LCD's for the MFD's. When i run a mission, at the mission start prior to clicking on Fly the HUD and MFD's are visiible and functional (behind the Briefing screen) but when i click Fly and the briefing screen disappears so does the HUD and the MFD's displays? This is both on the main monitor and on the external LCD's? Everything works fine when i fly in Open Beta on Viper and all other jets. Problem only affecting Viper in Stable. Any ideas guys? Thanks.

Hey, thanks for that! I didn't see the attached jpeg with the error message and also when i opened VA it downloaeded a supposedly new version, obviously not 1.8.7 though?? Downloading now!! Cheers.

Hi, I'm running VIACOM latest build with the A-10C II in Syria map, i keep getting this error and no commands are being sent to the sim from what i can tell? Even with simple commands like "2, go spread" etc. "1:00:06.254 UNABLE TO INVOKE PLUGIN, 'VAICOM PRO 2.5'. DUE TO EXCEPTION: 'VoiceAttack.VoiceAttackInvokeProxyClass' does not contain a definition for 'Dictation' Have done a web and forum search but nothing useful found so far to fix this? Any help appreciated. Thanks v much.

Interface Status Report { "Product": "Helios", "Version": "1.6.3308.0", "Items": [ { "Name": "Keyboard", "Report": [] }, { "Name": "Profile Interface", "Report": [ { "TimeStamp": "10/31/2020 03:15:19.606 PM", "Status": "Profile is not yet named", "Flags": 3 }, { "TimeStamp": "10/31/2020 03:15:19.609 PM", "Status": "The monitor arrangement saved in this profile matches this computer", "Flags": 3 }, { "TimeStamp": "10/31/2020 03:15:19.609 PM", "Status": "The profile declares a monitor of size 800x600 at (-2400, 0)", "Flags": 3 }, { "TimeStamp": "10/31/2020 03:15:19.609 PM", "Status": "The profile declares a monitor of size 800x600 at (-1600, 0)", "Flags": 3 }, { "TimeStamp": "10/31/2020 03:15:19.609 PM", "Status": "The profile declares a monitor of size 800x600 at (-800, 0)", "Flags": 3 }, { "TimeStamp": "10/31/2020 03:15:19.609 PM", "Status": "The profile declares a monitor of size 3440x1440 at (0, 0)", "Flags": 3 } ] } ] }

@derammo Just went onto your Discord as per your link and read the rules etc. Can't seem to send anything to you from there though? What do i need to do please? Thanks.

Hi derammo, Thank you for the kind offer, any help would be gratefully received! My setup is as follows: 5 monitor setup on DCS Desktop PC Main display is 3440 x 1440 on Display Port. 3 x Cubesim USB 3.0 LCD panels fitted to Cubesim backboxes and Cougar MFD's running at 800 x 600 these have a custom MonitorSetup.lua in order for them to work with my current setup, i will attach copy to this post. They also currently have to be arranged in a horizontal row from the top left of my main display to work with the .lua. 1 x Prechen 15" Touchscreen display at 1920 x 1080 (this is what i am obviously trying to put the UFC onto to utilise the touch capability etc Total desktop resolution = 5840 x 1440 in DCS monitor settings. Cubesim.lua selected from the Monitors options in DCS settings. I also have a MSI Gaming laptop which i tried connecting the Prechen Touchscreen to and then attempted to set up the remote PC Helios option to the main Desktop with, without success. I tried connecting the Touchscreen to the Desktop and setting up that way but it didn't seem to work, wherever i pressed the screen the responses were always received a couple of cms away from where i pressed. It also seemed that no keypresses were being sent this way either? Hope all of that is clear? Sorry!! Hope you can help, thanks again. Desktop image is at link below: https://ibb.co/k1GqZvk CUBESIM.lua file _ = function(p) return p; end; name = _('CUBESIM'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 2400; y = 0; width = 3440; height = 1440; viewDx = 0; viewDy = 0; aspect = 3440 / 1440; } } LEFT_MFCD = { x = 80; y = 0; width = 600; height = 600; } RIGHT_MFCD = { x = 880; y = 0; width = 600; height = 600; } CENTER_MFCD = { x = 1680; y = 0; width = 600; height = 600; } F14_HSD = { x = 80; y = 0; width = 600; height = 600; } F14_VDI = { x = 1680; y = 0; width = 600; height = 600; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

Hi, I wonder if anyone can help me solve this problem? I am trying to setup a DCS Hornet UFC export profile i have on a remote laptop with a touchscreen connected in order to send the UFC keypresses to my desktop PC that has DCS running on it. So far no problem with the laptop/touchscreen side, the profile works and when i press the UFC buttons on the UFC they are recognised (they derpress etc.) The problem is i do not seem to be able to get the keypresses recognised and active in DCS on the Desktop PC. I have the keypress receiver installed on the desktop and have configured the pots etc to match with the Helios install on both systems. I just have no idea where to go from here to get the touchscreen keypresses active in DCS when i'm in the Hornet. Unfortunately i can't use the more conventional method of connecting the touchscreen to my desktop system, i've tried but it just doesn't work. Any help at all would be very much appreciated, i have been working on this for a few days now. Thanks.

Hi there CaptKornDog, I had this same issue for years also! I was however able to solve it, albeit by using another piece of hardware i happened to have and some .lua code i found on the web. Even after this solution i still found there are some drawbacks that make it less than perfect for what most of us would want this toggle capability for. I own a Logitech G-13 Gameboard, it's a really great piece of hardware and i use it in many other games and sims. Through searching at length on You Tube and elsewhere i found out there is a Lua scripting capability with the Logitech Gaming Software that adds more advanced functions to the hardware and allows more options in your gameboard profiles. After much digging on the web and trial and error, i found a ready made script for the G-13 that enables turning any key on the board into either a toggle key or a hold key. This code will work on any Logitech input hardware (joysticks, keyboards, gameboards, even mouse i believe) that uses the Logitech Gaming Software. You can even add a message to be displayed on the devices LCD screen to tell you what key is currently active and when you deactivate it. It only take a few minutes of changing some text in an editor. It doesn't require ANY coding or programming knowledge at all. The main "slight" drawback with using this solution in terms of DCS sims is that when you press one of the toggle keys to access the Snap View, you can then only interact with that view (click OSB's, switches etc. with mouse clicks. You can not interact with it or use any other joystick or keyboard commands while in the Snap View. This is obviously due to the G-13 generating constant presses of the LWin + KP0 etc key and therefore not allowing any other buton or key presses to be generated/read by the sim. As far as i know there is no way around this unless someone on here has a solution. Maybe altering some of the default DCS keyboard .lua file code might work? I don't have the knowledge to do that myself and am not going to try! For any Logitech hardware users out there i'm happy to post the .lua code for your hardware to enable this capability? It's not mine, and dates back to 2013 i believe? It's very easy to set up for your hardware if you read the instructions at the top of the code itself. Happy to pass on and help with set up if anyone interested. :pilotfly::)

Yeah i see what you mean! all sorts of weird stuff going on as it loads? I'll maybe give that program a run at my install and post some results but as you say the list will be very long and not that conclusive in terms of identifying any workable remedy? Thanks.

So, here are my DCS load time results. Load time from desktop click to Main Menu Screen: With DCS 2.5.4 Open Beta, Flaming Cliffs, jsAvionics and Tacview enabled = 18 seconds. AV8BNA Harrier re-enabled = 18 seconds. F-14B Tomcat re-enabled = 18 seconds Breathes sigh of relief as these are the main 2 modules i currently fly!! So no appreciable difference in load times for these 2 modules then? I left the above 2 modules enabled for remainder of tests. Each of the below modules was enabled, timed and then disabled prior to the next module being tested: F/A-18C Hornet = 58 seconds. A-10C = 1 minute 16 seconds. F-86 Sabre = 43 seconds. FW-190D = 43 seconds . Spitfire IX = 18 seconds. Su-25 Frogfoot = 18 seconds as above adds no additional load time. Bf-109K = 1 minute 37 seconds. F-5E Tiger II = 43 seconds. M2000C Mirage = 18 seconds. Black Shark 2 = 43 seconds. UH-1 Huey = 42 seconds. Combined Arms = 23 seconds. WWII Assets Pack = 18 seconds. P-51D Mustang = 1 minute 1 second. TF-51D Mustang = 18 seconds. Terrain packs (Caucasus and Persian Gulf already enabled). NTTR = 18 seconds. Normandy = 18 seconds. Then tested time with all 4 terrain packs enabled = 18 seconds. So it would appear that on my system terrain packs add no additional load time to starting up the sim. Final results: It appears then on my system the following 4 modules add an extra 3-5 minutes approx. to the overall load time of the sim: F/A-18C Hornet A-10C Bf-109K P-51D Mustang My baseline start up time without the above 4 modules and with Harrier, Tomcat, FC3, jsAvionics and Tacview enabled is between 18 and 43 seconds depending on which additional modules are enabled. With ALL the modules listed above that i own enabled minus the 4 slower loading ones start up time was: 01:50 minutes. So in conclusion i will be disabling all modules except the terrain packs, Hornet, Harrier, Tomcat, jsAvionics and Taview in order to keep my load times under 1 minute which i can happily live with. As expected and as mentioned in an earlier member's post on this thread, the more modules you have enabled, the longer load times you generally experience (system specs dependent of course). So, if you are experiencing this issue try going into the Module Manager and disbling the modules you use less frequently. Thanks for all the help and please feel free to add further observations and comments below if you like?

Ok!! Success!! The very long load times i have been experiencing are indeed to do with one or more of the installed DCS modules i have. I just went into the Module Manager and disabled everything other than Flaming Cliffs, jsAvionics and Tacview and disabled NTTR and Normandy leaving just Caucasus and Persian Gulf terrains enabled. Desktop click to Main Menu screen now...... less than 10 seconds!! I will now be re-enabling each module one by and re-starting to find the guilty modules. Will post results when done. Thanks.

@hollywoodvillain Yeah that's the same as me! I kept getting asked to enter an activation code for Flaming Cliffs but i thought i only had FC on my Steam version of the sim? Anyway, i logged into my ED account and saw i did in fact have a key for the non-Steam version of FC. So i obviously activated it, but it didn't solve the problem of the excruciatingly long load times! And yeah, DCS.exe just sits there idling forever...... Am just going to live with it for now like you, but may do a re-install down the road and activate each module one by one, do a start up and see if i can locate the culprit? Thanks.

Windows is on another SSD but not the NVME. That would have required moving my Windows install as i only acquired the NVME about a month ago. Not a road i really want to go down unless absolutely imperative? 3-4 minutes from Desktop icon click to arriving at Main DCS program screen i.e. where i can choose Instant Action, Mission Editor, Multiplayer etc. etc... I can load a IA Mission or Single Mission etc. in about 10-20 seconds every time from click to cockpit. Thanks.

Working today so no time to look at this until tomorrow now anyway.

@rudel chw Thanks mate, i wasn't aware of that. Absolutely no intention of re-installing Windows so if i don't have to deactivate and so on then that's great. @etherbattx Thanks. There was no swap file active on my I: drive, so i switched to System Managed and tested but it made no appreciable difference. So i then created a 32GB swap file in I: but again after re-boot and re-starting DCS it made little to no difference. Start up still taking around 3-4 minutes as it stands. I am leaning towards a full DCS re-install to be honest, i think i have to at least try that as nothing else seems to be improving things. Thanks again for all the help guys.

@epoch Yes, my mistake. I managed to run the Cleanup and Repair thanks to the post from @MurderOne. Thanks anyway.

Just realised as well, can't really do a re-install as i'll lose a load of activations on my modules? Think i've only got 1 left on a couple like A-10C.... Bugger!!!

@Gruman No mods running since doing Cleanup and Repair earlier this afternoon.