Cowboy10uk

Hi all, now we have finally gotten to the point in Hotas addons that we now have multiple options for handles depending on what aircraft we are flying, I’m just wondering how people are storing any handles that they are not currently using. For example, I currently have the A10, F18 and Virpil F14 handles, that cover the vast majority of the aircraft I fly, and when not in use each handle has its own cover it sits in, but then just lays on the desk. I can’t help think there has to be a better solution like a stand of some sort that you can just screw them onto to keep them safe and on display while not taking up lots of room. I was just wondering what solutions if any, others have come up with in our community. I am guessing I’m not the only swimmer who now how additional handles just laying around everywhere.

Currently working my way through the campaign as we speak, it’s a fantastic campaign especially to learn the MI8. While I appreciate blowing things up and making big bangs is what most are here for, personally for myself, using the helos as the utility craft they are meant for and doing ass and trash missions like the ones in this campaign, are really where I get the true enjoyment out of the helicopter. I just wished we had more campaigns like this one, that shows off the standard work of the Helos, and one for the Huey especially. A medivac campaign, slick driver etc. Argo is great but low and behold they stick the darn weapons on and turn it into the gunship model half way through, which for me ruins it. Huge congrats for doing a civilian campaign. Thankyou, Best campaign in DCS as far as I’m concerned

Just did this mission yesterday, yes it isn’t clear at all where they want landing, I ended up doing a grid search for a good 20 mins until I spotted the oil Derrick. For those who don’t want to do the grid search, once you fly north over the mosque, turn left about 45 degrees and fly for a few mins, you will come across a clearing with a Derrick in the middle of it. Easier to spot if you have a good amount of altitude.

Having a similar issue, just trying to setup my DLC axis using the WarBRD base. It sees the switch as a button, and if I manually set it to slider 2, it shows input in the axis screen, but whatever I do, it won’t control the dlc in game. I’ve tried using it just as buttons and just as axis, and even both. Both the DLC remains stubbornly down

Damn, ok that was a simple fix. ???????????????????? Thankyou, I had thought I tried everything, never occurred to me to check if it was full screen or windowed. Damn. :doh::doh: Thankyou.

Ok then, good news is I’ve got the resolution and everything displaying and exporting to Helios great. The bad news is I cannot sort out the fonts on the Ampcd export. Both are just a thick green mess, regardless of what settings I place into the indicator files. Ive tried reducing down the thickness to 0.01 and it’s still shows rather thick and blurry. All other mfds look bloody perfect, my files are as follows AMPCD_init.lua shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.05 shaderLineDefaultFuzziness = 0.05 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true MDG_strokes.def.lua stroke_thickness = 0.4 stroke_fuzziness = 0.2 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 0.4 DMC_outline_fuzziness = stroke_fuzziness * 0.2 DMC_stroke_thickness = 0.65 DMC_stroke_fuzziness = 0.42

Main one is 3840 x 2160, The touchscreen is 1920 x 1080. Combined I have the resolution set in DCS at 5760 x 2160

I’m just wondering if I can grab some help as I’m really really struggling to get the resolution right in game with my 2 monitors. Although Helios displays fine, it connects and shows the steam dials right and the mfd exports work a treat, my issue is the main menu is compressed up on the left side of my main screen and the cockpit view is compressed and only 3/4 across my main screen when I’m flying. As far as I can see my lua is fine, but something has to be wrong somewhere. Just wondering if anyone has any ideas what I’ve done wrong. _ = function(p) return p; end; name = _('2_monitors_FA18C'); Description = 'Right, Left, RWR, IFEI, UFC, and AMPCD in right monitor' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } --LEFT LEFT_MFCD = { x = 4095; y = 686; width = 395; height = 378; } --RIGHT RIGHT_MFCD = { x = 5076; y = 691; width = 387; height = 377; } -- RWR F18_RWR = { x = 5296; y = 1199; width = 200; height = 210; } --AMPCD CENTER_MFCD = { x = 4596; y = 1181; width = 368; height = 356; } --IFEI F18_IFEI = { x = 3896; y = 1247; width = 601; height = 209; } --UFC F18_UFC = { x = 4538; y = 493; width = 496; height = 323; } UIMainView = Viewports.Center GUI = { x = 0; y = 0; width = 3840; height = 2160; }

Hi guys, sorry for resurrecting an old thread. BUT I’m really struggling after deciding to setup Helios once again on my system. However I’m really struggling to get the menus and cockpits show in the right resolution on my main 4k monitor. The menus are squashed up towards the left when I start, which if I alt tab will then show full screen as it should. The bigger issue is when I enter the aircraft, the cockpit itself seems squashed and rather than displaying over the entire screen as it does when I select normal 4k resolution, the cockpit is only across 3/4 of the screen. When I select 5670 x 2160. My touchscreen is below the 4k monitor. Any ideas guys guess it’s been driving me nuts for the last 6 hrs. I just can’t seem to get the resolution to work. my monitor lua is as follows _ = function(p) return p; end; name = _('2_monitors_FA18C'); Description = 'Right, Left, RWR, IFEI, UFC, and AMPCD in right monitor' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } --LEFT LEFT_MFCD = { x = 4095; y = 686; width = 395; height = 378; } --RIGHT RIGHT_MFCD = { x = 5076; y = 691; width = 387; height = 377; } -- RWR F18_RWR = { x = 5296; y = 1199; width = 200; height = 210; } --AMPCD CENTER_MFCD = { x = 4596; y = 1181; width = 368; height = 356; } --IFEI F18_IFEI = { x = 3896; y = 1247; width = 601; height = 209; } --UFC F18_UFC = { x = 4538; y = 493; width = 496; height = 323; } UIMainView = Viewports.Center GUI = { x = 0; y = 0; width = 3840; height = 2160; }

Huge thanks for putting this together, just finished watching the twitch feed at work. Sshhhh don’t tell anyone. ;) Was a great little session, and got some nice little tips from Bio. He really sounds like a great guy and I’m impressed that he’s willing to give his time up for us. He’s certainly sold another copy of his 3rd book now, already have his other 2.

Because they also clearly stated there were issues it’s bugs in that very post, although a few paragraphs below the excuse of not releasing during the sale. We were all aware of the issues regarding the F14, although as thats a 3rd party project then yes it might take some time to get it dialled in. Do you honestly believe that these bugs just magically appeared at the weekend on the last build. ( surely if SC was purely delayed because of the sale as they clearly blamed it on, then how come it all of a sudden no longer works... ) Plus I never said the team has lied to us, I have just pointed out that by using the excuse that is was delayed because of the sale, rather than the fact it still doesn’t work right, they have now left themselves in a bit of a pickle. IF they now release before the 18th May, which is when this current sale ends, then they will go against their own policy that they stated they follow for releases only earlier this month. I.E. no new releases during sales. IF they don’t release before the 18th, then people will start questioning how on Earth ED missed their eta by so much. Is it bad management etc. They have put themselves between a rock and a hard place by not just being honest in the first place and clearly stating, sorry all, we still have some game stoping bugs with SC and we need to delay her a bit to get it right. Here is the post in question and it clearly shows 9 stoppers on the list, including the MP sync issues that is the reason for the current delay. https://forums.eagle.ru/showpost.php?p=4250396&postcount=1

I was just coming to ask this very question, given that the first delay, the excuse was used that they don’t release during a sale, now granted we all know that was just an excuse and the real reason was it just wasn’t ready. BUT now they have openly stated that, are they gonna stick to it, which means no chance of getting the SC before at least the 18th May, or are they gonna decide to ignore that ruling and release anyway, knowing that will go against the policy they just told us about... :huh::huh::huh:

No it’s been delayed, until sometime April / May. No current eta though

KC135 speed adjusted for F16 usage??? Does this mean it’s gonna be too quick for the A10? I appreciate the A10 has a long loiter time, but I do enjoy practicing A2A refuelling with her while on missions. Problem is she’s such a slow aircraft, you can really struggle catching up to the tankers while fully loaded. Really wish there was a way to adjust the tanker speed on the fly depending on which aircraft you’re refuelling at the time.

I actually find the harrier is the easiest once you learn where the hose should be in regard the left mirror, the Hornet I can connect most of the time, the tomcat is just a bugger, jumps all over the damn shop and won’t stay connected for more than a few secs. Strangely enough after learning basket refuelling for a while, I’ve recently gone back to boom refuelling with both the A10 and F16, and I’ve found that is relatively simple, just formate on the tanker, and they do everything else including following your aircraft about. Biggest issue I’ve found with refuelling the A10 is catching up with the damn tanker. Damn that thing is bloody slow.

Personally I love them both, but I do find myself flying the Hornet more. Purely and simply because the Hornet is more forgiving with my rubbish piloting skills, and the fact that currently she is more versatile when it comes to weapons carried. Don’t get me wrong the Tomcat wins hands down in the beauty aspect of the competition and the work that has gone into the Jester AI is mindblowing. But she really is a pilots machine, and the workload is significantly higher I find than the Hornet. That said, if you can master the Tomcat on the battlefield, then any other aircraft in DCS should be a synch to fly.

Just bumping this, had the same issue last night on a MP server. Cold and dark startup on carrier, taxied and hooked up fine, powered up, salute and nothing. As it’s been ongoing for what looks like almost 6 months, any chance of an update please. I’ve only just started learning the F14, hence why I’ve only just come across this issue. But not being able to use a carrier aircraft, on the carrier, is kinda a major issue

Sorry it’s FIXED the cat launch issues. Excellent does this mean, we can finally do cold and dark startups again on the carrier. Was a tad annoying when the salute wouldn’t do anything after hooking up.

IDS hands down please.

This is just an amazing opportunity for the community, I know not everyone wants to play as a Rio, but for those of us who do, getting training and info from a real life top gun instructor. Damn, I never thought that would happen. Hell I know I’m still gonna be rubbish at it, but at least now I know I’m rubbish with no excuse. :D :D

Ok guys, we all know the Supercarrier has been delayed, BUT it looks like our fears about the F14 not working on her, may be a thing of the past. Literally just patched in the last hr, on today’s open beta patch From the F14 section Disabled AI kneeling (for supercarrier) Added holdback bar (for supercarrier) Added salute command (for supercarrier) Supercarrier compatibility added for client/player WIP: F-14B AI compatibility for supercarrier Woohoo, that does sound rather positive. Thanks guys.

Just been using the gulf version of this today, and must say it’s a great mission for learning the ropes on Thankyou, just one thing however I tried A2A refuelling today with the A10, and couldn’t for the life of me catch up to the KC135, is there a way I can slow it down to match the max speed of the A10. I managed to get the A10 up to 220 kts but the tanker was still pulling away, I think he said he was at 270, which I had no chance to match when fully loaded. Hell even after dropping all stores I could only get to 240

Sadly not gonna happen, although I guess you already know that by now. She’s delayed without any new release date, the best is April/May 2020, so realistically plan on final day of May, and anything sooner is a bonus.

+1. Well said sir.

To be fair, if they didn’t care, they would have released it bugs and all just to make a release date, and to hell with us if it didn’t work right. They obviously want the module working well enough so it can be usable, and while I get the fact it does state the main no go was related to MP side of things, I wouldn’t be at all surprised if there are other issues relating to the SC in general. Yes it’s disappointing especially as they didn’t let us know till day of release, certainly I was talking enthusiastically about using this for our weekly flying session tonight, and how amazing it would be and then I checked the forums.... ????????????????. The plans have obviously changed for tonight’s flight now bugger. I get that a lot of people of stuck at home in lockdown across the world, and were looking forward to this as an escape and having the time on their hands, they could have really put it through it’s paces, but sadly these things can happen, and even though you can do programming from home I’m sure, we have no idea how the virus has effected EDs work force, and can any of us honestly act surprised that things have been delayed in this current climate. I bet all the programmers at Ed, who have been working their butts off to get this to us, are as disappointed if not more than us about the entire situation. IF they released it with the current issues, then they would end up spending every day fighting off the complaints that it doesn’t work correctly and why did they release it in this condition, it’s a situation that which ever way they went they were screwed. Could it had been communicated better, YES. Were they aware it would likely be delayed 3 days ago, after the weekend test, YES quite possibly. But obviously they were trying not to disappoint us and I guess put all their eggs in one basket Hoping to get a solution in time, which has back fired somewhat.