Robin885

Hi, I've recently finished mission 14 which I must say, was one of my favourite missions I have flown in a DCS campaign, head on a swivel for more than an hour. However, I was running on fumes at the end because bucket refused to give me more than 500 pounds at both the ingress and egress. In both cases Olive tanked first and got her 3k, and I was left with only 500 or so. He then retracted the basket, and disapeared from the comms menu.

Hi, I recently bought a new PC and planned to use DCS at it's full potential. However, I find the Extreme Visibility Range setting to just not be enough. Hence I started to look for ways to improve it by fiddling with the lua files. I managed to find the graphics.lua file in the installation and modified the extreme setting from 1.5 to 3. Now 3D models do load further than before however, if they load in the distance, then closer ones will disappear, making it very weird looking. So, I'm asking here is there anyway to properly buff the visibility range in DCS? I noticed a readme file with the graphics.lua explainging that we should now create a autoexec file the the saved games but I couldn't make it work. Here what it looks like with the corresponding setting: distancFactor = { Extreme = 3; distancFactor = { Extreme = 1.5; There it is. As you can see, the top picture does have a further visibility distance but the closer 3D models just don't appear. Does anyone have any idea? Thank you very much.

Yeah I do have this noisy/grainy effect on screen too. I can’t find where it’s coming from, I did a full DCS reinstall but it did not fix the problem.

Hi everyone, I'm not sure if it's a bug or not, I'm posting here to get the opinion of others. Since the 2.9 update came out, I noticed a decrease in the visibility distance of terrain objects (building, houses, trees, vegetations...), and I feel like it is much lower than before. I spent two days fidling with the graphics in-game, trying to make sense of the FAQ regarding the changes in 2.9, but I just can't make the game look like it did before the update. Note that the visibility distance option does work, there is a substancial difference between low and extreme, yet it looks like it was downgraded at all options. Also, I have the impression that a grain effect has also appeared on screen and I feel like it comes from the vegetation's shadows. Once again, I'd like to have the opinion of other players to see if I'm just acting psychotic or if something did changed. I also tried to fiddle with the options but couldn't find a good setting. Thanks and have a lovely afternoon everyone.

Unfortunately, given the fact that I have very little time to access my setup, I wasn’t really wishing to spend more time on it. I understand this is an ED problem, and I will be sure to come back to it once it’s fixed, or when I have the time to troubleshoot it. I love the P-47 and your campaigns are beyond awesome, so be reassured that I will go through it eventually However, as I was looking for people on the forums having the same problems, I came across your "Fortresses over Europe" multiplayer mission. I’ve spent all the rest of my weekend playing on it, it was awesome. Are you planning to make a similar mission when Normandy 2 comes out? Long range escort missions in multiplayer is just one of the things I would love so much.

I tried going as fast as I could, Halstead Red 1 and 2 managed to taxi without trouble, but my element lead wouldn't move as the other P-47s were taking off at the same time. So we had to wait a solid 3-4 minutes before crossing the runway to taxi to the takeoff point. Unfortunately by that time another P-47 flight was waiting aswell and so I was stuck with the same bug, except it was Red 3 that was stuck this time, not Red 1.

Thank you for the quick answer. I will try saying I'm ready earlier, and warm the engine on my way to the runway. A temporary fix is better than no fix

Hi, I've just bought the campaign after the 2.8 update, but on the first flyable mission the AI won't takeoff after taxiing. I'll retry this afternoon, but it looks like the mission is over before even starting without being able to takeoff.

Concur, and it actually does it when the button is bound to a RIO keybind too. As the pilot keybind overrides it, RIO Keybinds do not work as they affect the pilots buttons instead.

Pilot: JTFF | Robin | 354th Rio: JTFF | Kilowatt | VF84 F-14A

Well you guys are saving me some time, I'm playing the mission right now and just noticed while sneaking in the F2 view that the hornets weren't there anymore

It's been quite a long time now that we haven't had any news regarding further updates to the A-10CII, especially regarding the ARC-210. I'm hopeful this will add the ability to edit radio presets in the mission editor too. Is there any way we could obtain any info regarding the state of the module? Or are any news comming soon?

It’s been a long time now, but what I was doing was pitching up ~20°, at a range at which my piper would meet my zone to illuminate in the distance when I pulled up. It worked relatively good, but it’s very impractical. I find them much easier to use in the russian choppers, as they deploy sooner

Currently, there is an option to disperse the elements of a group/convoy when they are fired upon. My question is, is there any way to manually do that while playing as the ground commander/JTAC on the F10 map? My problem is I am making a mission where I would like my convoy to disperse in the nearby trees to stay hidden while helos pass over. But I can't see anyway to do that except if I fire on the convoy.

I'm pretty sure this has been mentionned before but I haven't managed to find any post about it. Currently the Mi-8's blade stall will force the helicopter to bank left, while I believe it should actually bank right, as the retreating blade on the right side of the rotor disk. Terminus, who does excellent Hip tutorials, covers this bug in his blade stall tutorial (I set the timestamp):

We were actually wondering if it was a bug or us doing a bad manipulation. Turns out it was the latter, thanks for the heads up^^

We all know it will be an F-111F or C, right heatblur?... right?...

Very interesting read. So far in DCS the parachute deployment process starts 17s after the rocket was fired, and travels approximately 5 to 6km before opening from the tests I've done, sometimes a little bit more. The figures are much higher in DCS than described here. So as I understand it, the deceleration process starts after the ninth second, and by the 13th-14th second the parachute is fully deployed. Given that DCS doesn't model the whole chain of events and the rocket will go from it's standard velocity to 0 almost instantly, aiming for a value between 9 and 13 would be a good workaround, that's probably a way of doing it. But currently in DCS the rocket flies too far and for too long

Possibly, it would make sense too.

The Huey has parachute illumination rockets available as a loadout, and they work great but there's a hick. The parachute deploys from the rocket after 17 seconds of flight time, which makes them very hard to use, and even harder to aim properly. Modifying the timefuse in the game files breaks the Intergity Check unfortunatly. I believe this is something that should be manually tuned on the ground, is there anyway we could have an option for that? Or just simply reduce the timefuse from 17s to 10 or 8s, which makes them much more comfortable to use. Thanks

Hi, Is it possible to get an update on the 2 other models for the Tomcat? I guess this question is fairly redundant but we haven't got any update on this topic since the A late model came out. Thanks

Hi, I've watched Redkit's preview of the campaign, and it's said at the very begining of the video that the campaign can be played with a full crew. Is it something we have to edit in the editor? Couldn't find the two player version so far. Thanks Nvm, I didn't realise it simply needed to be started in MP since it's just a single plane anyway.

Little off topic, but have you enabled guard reception on the radio you wish to use in the hornet via the UFC? Otherwise it won't work I can confirm however that it doesn't seem to work in the Tomcat

Either a desert storm era F-111F or a late F-111C. They are the ones I'm rooting for the most.

It appears that fixed the issue, I can now join and hop in the cockpit without incident. Thank you about that.