Cowboy10uk

I’m keeping everything crossed it’s significantly better. 2.0 is a slideshow with anything more than a few units for me at the mo. Current.y stuck in 1.5.8 as that stills plays nicely with my machine. Part of me is excited for 2.5, but quite a bit of me is petrified that I might end up grounded until I find the money for a new rig, and that certainly won’t be this year. Cowboy10uk

Don’t worry mate, I asked the very same question, and did excatly the same thing yesterday. :doh: Glad she’s working for you now. Cowboy10uk

I was using Notepad, I know I know, It’s not well liked. I have however downloaded notepad ++ yesterday so will use that from now on. Cowboy10uk

Gliptal you are a bloody genius. After walking away for a beer and came back and saw your reply, so took a another look, a closer look going letter by letter. discovered a missing } just after the last line on the right MFD, entered it, saved and not only is dcs now seeing the file, the GUI is also working. I guessing that the GUI was still using the default single monitor config that appears to have the same name, so while I was thinking it was using my one, all the time it wasn't seeing it at all. Anyway, thanks again, I may have missed my flight window by a good 2 hours but at least the darn thing is working and working well it appears. Rep incoming Cowboy10uk

Pete, you are fantastic as always cheers mate. Cowboy10uk

Hi guys, before the latest patch she was working fine. But now once I get her all started up, I increase me throttle and see it move in cockpit, but I get absolutely no increase in rpm or movement on the aircraft. Any idea what I’m doing wrong cause it is driving me nuts. Cowboy10uk

ok guys, I surrender. I cannot for the life of me get the GUI working on just the main screen of 3840 x 2160 and now just to add another complication into my life, the file I was editing is no longer seen by DCS so I cant select it via the drop down menu. Tried the last fix which worked last time, but that isn't working either. my mfd export.LUA is below, could someone please please kindly look at it and either tell me where I went wrong, or even better fix the darn thing. Cowboy10uk mfd export.lua

G'Dammit, windows just did an update and now I'm back to square 1 with the GUI spread over both screens again, meaning once again I cant access most of the buttons, and now the darn GUI tweak doesn't even bloody work. :mad::mad::mad::mad::mad::mad::mad: Cowboy10uk

I know, I just couldn’t see the issue for love nor money, despite setting up several multi monitor systems in the past. Now Xoxen kindly pointed that out it was blooming obvious, but damn was it doing my head in. At least the age old rule still applys here, if all else fails and you’re about to throw the pc out the window, swallow your pride and ask the forums for help. :thumbup: Cowboy10uk

Damn youre fantastic. That bugger has been keeping me guessing for the last 5 hours. Now it all works. THANKYOU Mate :thumbup::thumbup::thumbup::thumbup: Cowboy10uk

Hi guys, I'm sorry but I need your help. Can someone have a look at my monitor lua file and let me know where on earth Ive gone wrong. I'm running a single 4K TV at 3840 x 2160 and a small 1920 x 1080 screen for my mfds. The mfds export beautifully onto the second screen, But the GUI ALWAYS expands across to the 2nd screen as well the moment I select 5670 x 2160 res in the settings menu, which I need to allow the mfds to be exported. I cant for the life of me get the GUI to only be displayed on the main screen. any advice or help would be very greatfully recieved _ = function(p) return p; end; name = _('mfd export'); Description = 'One monitor configuration' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 3845; y = 75; width = 854; height = 854; } RIGHT_MFCD = { x = 4904; y = 76; width = 854; height = 854; } --CDU_EXPORT --UIMainView = Viewports.Center GUI= { x = 0; y = 0; width = 3840; height = 2160; }} Cowboy10uk

:megalol: you wouldn’t be saying that if you’ve ever seen me fly. :thumbup: Cowboy10uk

That looks pretty cool, I know when I’m gonna be testing lasted on. ;) Cowboy10uk

Yep that what I thought, it showed absolutely nothing and acted as if there was nothing wrong with the gear, I only realised the nose gear was stuck down, when I went outside for a screen shot. Will try and test it again and get some shots. Should be easy enough with my flying. ;) Cowboy10uk

Sadly I believe he’s busy with RL until next year, I’m afraid we might have to cope with this one on our own. However I can’t disagree, Chucks guides are the best in the business. Cowboy10uk

^ this, I tried to add a Tacan when I placed her onto the map, but there doesn’t appear to be an option for it. According to this page, she does carry tacan in RL. https://fas.org/man/dod-101/sys/ship/lha-1.htm Cowboy10uk

Hi guys, practicing my landings a made a particularly hard landing which resulted in my nose wheel being unable to retract and stuck in the down position. However the gear warnings lights in the cockpit showed the gear was locked and raised normally, and when I lowered the gear, it then showed 4 greens. Isn’t it supposed to show Red in a particular gear is in an unsafe configuration? Can upload a photo of the gear in an external shot later on, when I get my phone back if that’s ok. Cowboy10uk

Ok so Comm 2 to ME to get comms up, is that right. Don’t really want to have to keep going into settings switching easy comms on and off all the time, as generally I don’t use it. Cowboy10uk

Ahhhhh that would explain a lot, thought I was just being stupid. :doh: Cheers mate Cowboy10uk

Hi guys, I’m having a slight issue with the radios, I can’t for the life of me get them to talk to anyone. I’ve programmed the correct freq into the mission manager for my tankers. 131,132 & 133 MHz on comm 1, I turn on radio, select relevant preset on ufc, it shows correct freq, I select comm 1 on my hotas and transmit, I get nothing whatsoever. Same happens when I try and contact tower. Anyone any ideas, or am I just being an idiot. I just can’t see where I’m going wrong. Cowboy10uk

Hi guys, appreciate this appears to be mainly triple screen setups, but may I ask if this technique would also work for a 4K tv and a small monitor to display my mfds on. I am using a 55” 4K tv at 3840 × 2160 and have just purchased a small single monitor running at 1366 x 768 to display my MFDs on with the Cougar MFDs taped over the screen. Am I right in assuming, that I can use this same technique to make this work. I’m assuming that I just add the 2160 & 768 together to get my width and 3840 & 1366 for my height? Cowboy10uk

Hi guys, just a quick question. Is it possible to export the MFD displays to a 2nd screen, similar to how it works with the A10 and Blackshark? Hoping to setup a couple of cougar mfds on a small 12” screen in the near future. So hoping I can set the Harrier up on the same file as the A10 as both would use identical settings, apart from mfd name I’m guessing. Cowboy10uk

:O wow, now that would be bloody amazing. :thumbup:

Engine goes pop, and you go into the ground like a lawn dart. At least I did anyway ;) Thought I would test the EGT limits and see if they really did affect the engine. Mmmmmm YEP. Very well done Belsimtek. Cowboy10uk

Go to start, Eagle Dynamics and update openbeta. Oh and make sure you’re on openbeta, as it’s the only version she’s on at the mo. Cowboy10uk