Cowboy10uk

Hi guys, does anyone know of any good coop missions I can use for practicing sling loads in 1.5 or failing that, how easy is it to add a few loads into a previous practise mission I've already made? Want to get practising them with the MI8 AND Huey. Cowboy10uk

Anyone ever tell you sir, you are bloody fabulous. Nice easy solution I didn't even think about, was too focused on the A10 settings, never occurred to me, to just adjust the Blackshark and describe them as they are. :doh: Problem solved, all exports working well together and all Helios profiles are setup. Now where's that Republic campaign. :) Rep incoming, thanks for all your help. Cowboy10uk

It's whatever LUA file, you have setup for your Helios mate, should be in config, monitor setup, Many thanks I appreciate this. Cowboy10uk

Hi there, thanks for the advice, sadly that didn't work all it did was swap the A10 mfds to the BS sizes. Looking at it, I'm sure it's because I have the same name, right mfd and left mfd for both A10 and BS. I've tried the ones suggested by PeterP a while ago, but sadly can't get that to work, nothing outputs then. Guessing ED has changed the names again on an update somewhere. Anyone know what the new names are? Cowboy10uk

Hi mate, my screens are setup in a T configuration. With 3 x 1920 x1080 on top, setup as one screen via Nvidia Surround, and then a 1920 x 1080 touchscreen underneath the centre screen setup as the accessory screen via Nvidia Control panel. In DCS, resolution is selected as 5670 x 2160 via settings. No bezel surround has been added. Helios is open on the bottom screen, and all exports are setup to display on the bottom one. I'm using Loz's A10 profile and ALL Capt Zeen Profiles. All the height and width settings above fit the profiles perfectly. The only issue I'm currently having as you're aware, is the A10 MFD sizes are being displayed when the KA50 profile is being used, although output is current. However, IF you block the A10 MFD settings in the LUA, change the export name works, then the Shkval and Abris display with correct sizes. ( trying to track down that conflict ) As you only want KA50 sizes, then if you use the Shkval and Abris Width and height settings from my LUA, then it should match the profile perfectly. Obviously the X and Y settings, will only work for a screen setup the same as mine. Hope that helps. Cowboy10uk

Hi all, I'm just wondering if anyone has managed to get this profile and Loz's A10 profile working together utilizing the same monitor.lua file. I have all exports working no problems, whatsoever for both aircraft however the A10 MFD size appears to conflict with the KA50 Shkval and Abris size, and when both are in the monitor file, The Shkval and Abris exports at the A10 MFD size. When no A10 MFD export in Monitor.lua then Abris and Shkval display at correct size. Ive just tried using ED_A10C_LEFT_MFCD and ED_A10C_RIGHT_MFCD as names but now the A10 MFDs display at the KA50 Size's. I know Sobe is having a look later today for me, but if anyone else has an answer as well for me to try I would be greatful. Meant to be flying in 60 mins This is what I have in the LUA file so far. _ = function(p) return p; end; name = _('2_monitors_KA50'); Description = 'Right MFCD on the right and camera on the center' --MAIN GAME VIEWPORT TOTAL SIZE AN ASPECT Viewports = { Center = { x = 0; y = 0; width = 5760; height = 1080; viewDx = 0; viewDy = 0; aspect = 5.3333333333; } } --SHKIVAL LEFT_MFCD = { x = 1930; y = 1080+0; width = 800; height = 670; } -- PVI800 MFCD_03 = { x = 1935; y = 1080+680; width = 240; height = 100; } --ABRIS RIGHT_MFCD = { x = 3252; y = 1080+0; width = 590; height = 840; } --EKRAN MFCD_04 = { x = 3100; y = 1080+990; width = 100; height = 60; } --UV26 MFCD_05 = { x = 2845; y = 1080+545; width = 150; height = 60; } RIGHT_MFCD = { x = 3330; y = 1205; width = 445; height = 445; } LEFT_MFCD = { x = 1990; y = 1205; width = 445; height = 445; } CMSC_SCREEN = { x = 2775; y = 1220; width = 230; height = 49; } CMSP_SCREEN = { x = 2995; y = 1265; width = 270; height = 70; } RWR_SCREEN = { x = 2520; y = 1240; width = 175; height = 175; } DIGIT_CLOCK = { x = 2400; y = 1910; width = 122; height = 122; } UHF_FREQUENCY_STATUS = { x = 2555; y = 1640; width = 120; height = 30; } UHF_PRESET_CHANNEL = { x = 2670; y = 1555; width = 30; height = 30; } UHF_REPEATER = { x = 2575; y = 1775; width = 110; height = 30; } UIMainView = Viewports.Center Cowboy10uk

Hi mate these are the settings I'm using in my LUA. It fits the Profile perfectly, sizes for both Loz's A10 Profile and Capt Zeen's KA50. Bear in mind this is for a 4 screen setup 5670 x 2160 Helios screen IS 1920 x 1080 Hope this helps. Cowboy10uk _ = function(p) return p; end; name = _('2_monitors_KA50'); Description = 'Right MFCD on the right and camera on the center' --MAIN GAME VIEWPORT TOTAL SIZE AN ASPECT Viewports = { Center = { x = 0; y = 0; width = 5760; height = 1080; viewDx = 0; viewDy = 0; aspect = 5.3333333333; } } --SHKIVAL LEFT_MFCD = { x = 1930; y = 1080+0; width = 800; height = 670; } -- PVI800 MFCD_03 = { x = 1935; y = 1080+680; width = 240; height = 100; } --ABRIS RIGHT_MFCD = { x = 3252; y = 1080+0; width = 590; height = 840; } --EKRAN MFCD_04 = { x = 3100; y = 1080+990; width = 100; height = 60; } --UV26 MFCD_05 = { x = 2845; y = 1080+545; width = 150; height = 60; } RIGHT_MFCD = { x = 3330; y = 1205; width = 445; height = 445; } LEFT_MFCD = { x = 1990; y = 1205; width = 445; height = 445; } CMSC_SCREEN = { x = 2775; y = 1220; width = 230; height = 49; } CMSP_SCREEN = { x = 2995; y = 1265; width = 270; height = 70; } RWR_SCREEN = { x = 2520; y = 1240; width = 175; height = 175; } DIGIT_CLOCK = { x = 2400; y = 1910; width = 122; height = 122; } UHF_FREQUENCY_STATUS = { x = 2555; y = 1640; width = 120; height = 30; } UHF_PRESET_CHANNEL = { x = 2670; y = 1555; width = 30; height = 30; } UHF_REPEATER = { x = 2575; y = 1775; width = 110; height = 30; } UIMainView = Viewports.Center Any chance someone can point me in the direction where I went wrong. Everything is working great apart from the Height and Width for the BS Shkval and Abris, which is using the A10 MFD Height and width settings. pretty sure I'm close, but ive been staring at this for the past hr, and ill be damned if I can see it. Need a fresh pair of eyes. Cowboy10uk

Hi Guys, Need a bit of a hand here please. I'm trying to setup a Monitor LUA that exports the MFDs and various displays from both the A10 and BS, So I can just swap between aircraft and helios profiles as I wish to fly them. Ive managed to get ALL the exports working and displaying in the right location, However since I added the A10 Exports to the file, The BS Shkval and Abris and being exported using the A10 MFD Sizes, rather than their own. If I take the A10 MFD Settings out they display normal again. This is what I have in the LUA file so far. _ = function(p) return p; end; name = _('2_monitors_KA50'); Description = 'Right MFCD on the right and camera on the center' --MAIN GAME VIEWPORT TOTAL SIZE AN ASPECT Viewports = { Center = { x = 0; y = 0; width = 5760; height = 1080; viewDx = 0; viewDy = 0; aspect = 5.3333333333; } } --SHKIVAL LEFT_MFCD = { x = 1930; y = 1080+0; width = 800; height = 670; } -- PVI800 MFCD_03 = { x = 1935; y = 1080+680; width = 240; height = 100; } --ABRIS RIGHT_MFCD = { x = 3252; y = 1080+0; width = 590; height = 840; } --EKRAN MFCD_04 = { x = 3100; y = 1080+990; width = 100; height = 60; } --UV26 MFCD_05 = { x = 2845; y = 1080+545; width = 150; height = 60; } RIGHT_MFCD = { x = 3330; y = 1205; width = 445; height = 445; } LEFT_MFCD = { x = 1990; y = 1205; width = 445; height = 445; } CMSC_SCREEN = { x = 2775; y = 1220; width = 230; height = 49; } CMSP_SCREEN = { x = 2995; y = 1265; width = 270; height = 70; } RWR_SCREEN = { x = 2520; y = 1240; width = 175; height = 175; } DIGIT_CLOCK = { x = 2400; y = 1910; width = 122; height = 122; } UHF_FREQUENCY_STATUS = { x = 2555; y = 1640; width = 120; height = 30; } UHF_PRESET_CHANNEL = { x = 2670; y = 1555; width = 30; height = 30; } UHF_REPEATER = { x = 2575; y = 1775; width = 110; height = 30; } UIMainView = Viewports.Center Any chance someone can point me in the direction where I went wrong. Everything is working great apart from the Height and Width for the BS Shkval and Abris, which is using the A10 MFD Height and width settings. pretty sure I'm close, but ive been staring at this for the past hr, and ill be damned if I can see it. Need a fresh pair of eyes. Cowboy10uk

Thanks guys. Solved issue by uninstalling and reinstalling module

Hi guys, just tried the BS after a long time away, due to getting ready for the new Campaign. However I have noticed my Shkval keeps flickering on and off. I'm just wondering if anyone else has this issue, or if it's something on my side only? Currently running the latest nvidia drivers and DCS fully upgraded. I'm also running Helios with Cpat Zeens KA50 profile with the Shkval display being out putted. Cowboy10uk

Damn fixing Loz's A10 AND a UH1 Profile, happy days. You sir are a true hero of this community. Cowboy10uk

Well I was wondering if you could contact Loz and see if he would mind you updating his A10 profile, It's certainly the best A10 profile by far and nothing comes close to it, but sadly there are a few issues with the radio panels that have stopped working and would be great if they could get fixed. Or as many have said, having a profile of your standard for the Huey would be stunning, while we have profiles that allow for the switches to be accessed, it would be great to have the full gauges as well. That said, ANYTHING you decide would be great fully received, by the community. Would be a dream come true to have a full selection by you, and something I would be more than willing to pay for. Cowboy10uk

Damn, great job. Time to add the touchscreen back to my setup and get Helios working again. :) I need to try this. Cowboy10uk

Thanks for the replys guys, gives me something to start on at least. :) sorry it's taken me a few hours to reply, was rather hectic at work today, and didn't get a chance to log on. Cowboy10uk P.S. @ WildBillKelso, I primarily fly the UH1 and MI8

Hi guys, now first off I want to apologise straight away for what I'm about to say. I've been flying DCS since 2008 and I've always used simple radios. :doh: Main reason is while I can do cold and dark startups, use weaponry, program stores and hell, I've even been known to do some air to aîr refuelling, the radios have always scared me, as some huge complicated thing, that I really have absolutely no clue on how to use. So I've decided enough is enough, I need to conquer the beast. Now I'm sure I'm one of the few who use simple radios, so may I ask, what's the best way to learn these things, find out frequencies, and even know which radio is which. They all look the same to me? Is there any radio instructions out there like Chucks guides or is it just a case of playing around and seeing if I can get them working. Cowboy10uk

Fantastic, Rich contacted me on Monday to let me know my collective will be ready Tomorrow. :) Can't wait. Final payment sent. :) SwissMag, yes I did get in contact with him, he explained he's flying all week, and sorting out a house move so rather snowed under at mo. He is cracking on with the orders though. I'm sure he will be in contact with you as soon as he can. Cowboy10uk

Tough one, multi screen dosnt come close to the feeling of immersion that you get flying with the Rift, however certainly at the min, and quite likely with CV1, the resolution of the Rift is nowhere near where we as simmers need it to be able to fight effectively in sim. At the moment I would say stick with multi monitor, I know that's what I'm doing, however in a few years time IF they get the resolution sorted then I will be moving over to the Rift. Cowboy10uk

Hi guys, Now I see that the issue with the DK2 crashing in 1.5 has been mostly solved by a workaround found by Hellking, http://forums.eagle.ru/showpost.php?p=2507760&postcount=58 Can I ask if people are reducing their normal graphic settings when using the Rift or are they keeping them the same as if they were using the monitor. I know going in and changing all settings isn't that hard, but it would get rather annoying after a few times. Currently away on hols, so can't test this myself. Also what sort of frame rates are people seeing in 1.5, is it as much as an improvement as we are seeing when using a monitor. Cowboy10uk

Same issue here guys, running all settings on Max apart from DOF which is off, PC specs below in my signature, running PC with Windows 10 No civilian traffic anywhere. Cowboy10uk

:O Honestly what can I say, WOW. Ed has done a absolutly stunning job and Edge is looking georgous. Currently have all settings maxed, running tri screen at 5670 x 1080 on the spec in signature block. I'm getting a constant 60 fps when flying about, only two aircraft I've tried is the UH1 Huey and Mig15. I appear to be rather fortunate as all my modules appear to have installed correctly, certainly I think they are all showing, and all of my previous controls and missions worked straight away. Only one issue and that was with my Rift DK2 crashing after selecting fly, and I already know that's a known issue so not bothered about that. The new VR screen though is stunning, it really does work very very well indeed, can't wait to try the Rift once the drivers are sorted. Flying both slow and low or high and fast, the map looks amazing, the water is finally fixed and is now a joy to fly over, sadly only got to fly for about 45 mins as I've been at work. Will be putting a fair few hrs in tomorrow though. I did try and hit the trees in the Huey, sadly they are still not collideable, although thinking about it, I have a feeling Wags mentioned these were only collideable in the Nevada map. Well done guys, an amazing job. Cowboy10uk

Cobra, has just announced problem with Mig21 and 1.5 with it crashing. So maybe a mig 21 issue. Cowboy10uk

We may still have hope on that though, as it was on VEAOs list for a long time. I appreciate that they have since removed all Helos from that list, but I'm still quietly confident that we will see the Puma turn up once more. I love that aircraft, as I was pretty much brought up with it, my dad was a Puma Crewman for pretty much my entire childhood, and then I worked on them myself when I joined up. :) 33 Sqn, & 230 Sqn Cowboy10uk

full agreement here, Komodo are the way to go, Currently have a UH1 collective on order, hopefully being delivered within the next month or so. Will let you know how I get on with it, but after playing with the prototype at Weston, Damn its good quality. I cannot wait. :) Cowboy10uk

Stunning, the feeling of immersion and being in the cockpit is amazing, it really is the best immersion I have ever had on the PC. The head tracking is the best I have ever used, I have never had an issue of it dropping out or getting stuck, 1/1 head tracking really is the way to go. HOWEVER, and this is the important bit, with the DK2 the Resolution is still nowhere near where we are simmers need it, while you can read the dials to a degree, well you can see where the needles are. Reading any writing or numbers on the dials can be extremely difficult and forget fighting while wearing the DK2, you really can see well enough for spotting targets. General flying from A to B, fine no issues and is great fun, but target spotting, sorry forget it. Now I'm positive they will solve this, the jump in resolution from DK to DK2 was a fairly big one, and I'm expecting again the leap from DK2 to CV will be as big again. However I would certainly recommend holding off for now, until we find out for certain if the resolution is usable in the CV, realistically we need them to have the same clarity as today's 1080P monitors to make it usable, due to his close the screens are to your eyes then you're looking at 4K displays at an absolute minimum. On top of that, you will require a top of the range GPU to run it, as you really need an FPS of 80 to 100 to prevent sickness. A GPU that can run 2 x 4K screens at 80 to 100fps I'm not sure exists yet, unless you SLI a number of Titans. It WILL be the next big thing, IT will be hugely immersive, and yes it WILL be perfect for simmers, HOWEVER I still believe we won't get there until the CV2 or even 3, I will be very very surprised indeed if they solve the resolution issues with the 1st CV. Hope that helps mate. Cowboy10uk

Umm mm I've no idea, how would I check, and I'll have a look on Weds when I'm next getting a chance to fly, and post up here. Cowboy10uk