All Activity

He.... mal ne Frage. Hat vielleicht jemand den genialen Virpil FLNKR Grip auf der Moza Base oder auf Thrustmaster am laufen? Hatte ihn mir gegönnt und musste nun feststellen, das an der AVA Base kaum Buttons erkannt werden. Nur wenige... Sollte an der Moza Base alles gehen, könnte ich die dann doch mal ins Auge fassen.

thanks this has been reported and fixed internally for the next patch

Recived Today :).

OK, understood.

Yeah, this seems to be fixed. Thank you, devs!

AI behavior is a different story. 99% of the time, everything is fine, but you can hit that 1% where something goes wrong. In this case, it's hard to pinpoint the AI's problem. From what I understand, the AI is implemented so that if you don't move or you're on the ground too long, it automatically shuts down the engines after a while, but some time must pass. A typical start (checklist) with dialogues lasts about 5 minutes, and during that time, the AI doesn't shut down the engine (unless there's a collision in the DCS itself, which sometimes happens). As for the automatic end, it's fine, I'll keep that in mind for the future. However, as you noted, the SKIP option is active, so you can immediately replay the mission (especially since it's the very beginning, I think, so it probably took no more than 10 minutes) or move on to the next one.

Well, I don't have a problem with braking or turning in the Corsair. The curve I use is a J curve (something I used on the throttle in TARGET) and it works great. 0 90..... acts as a dead zone 0 -35..... The J curve The 90 is a dead zone at the top... What I have issues with is the spastic trim, especially the rudder trim. The slightest adjustment is like kicking the rudder pedals. I've tamed it somewhat with extreme axis curves. But don't get me started with low speed handling...... It is what it is; very early access, hopefully it gets fixed sooner rather than later. Because it has great potential......

I've previously suggested what I believe is a better solution: a true Open Beta—(implemented differently to before). Make it accessible only via command line, so only those with the tech knowledge of how to execute command lines, and also know the OB version number can install it. That way, it’s not used on production servers, and Open Beta versions don’t appear in the public server list—IP connect only. This would make it a genuine testing platform, not a general gameplay environment, and give us the time we need to adapt and see the upcoming changes and try them out. Sure - there will be some that push and opt to use it as a stable release, but it would be the minority. The previous OB didn't work because the majority used it as a stable release (and even ED recommended people use it for production in MP). I really feel we need a proper Open Beta for everyone’s sake. Far too many issues are being discovered in these new so called stable releases within hours, forcing hotfixes. That’s bad for both ED developers, who get blindsided and must scramble to patch, and for us, who have to react to breaking changes without warning. Let alone the image that it's putting out there of ED's quality. Let an Open Beta run for a couple of weeks—(1) to give content creators time to adapt, and (2) to apply necessary hotfixes—before pushing a public stable. Just a pity that ED seems to disagree that there's issues for the community by working this way and believe everything is fine as is. Nothing needs changing, with "no plans to consider...". While all along I see what I feared when open beta disappeared. That the new and improved stable release would eventually degenerate to being what Open Beta was all along - with no real practical alternatives for public server content creators (that aren't in the CB team anyway) to be proactive, and just have to be reactive and rush about to deal with bugs, problems, or breaking changes at the last minute.

dcs.logHere is my log. During this login session, the following issues occurred: the launcher took an excessively long time to open, there was a prolonged black screen while loading into the game, and the game's main menu froze and resumed multiple times.

Yes, I disabled the Virtualization Technology in the CPU settings under the BIOS. However, after performing this operation along with several other actions, issues such as a significant delay in launching the game via Steam, a prolonged black screen before the game loads, and even the program becoming unresponsive emerged. (I'm uncertain whether this is caused by the aforementioned operation.) Regarding troubleshooting by deleting the save folder, I've considered that as well. I've attempted deleting the DCS folder under the save game directory on the C drive and reinstalling the game to start fresh. Unfortunately, the problems persist when launching the game.

На джойстиках ВКБ можно настроить хатку на управление курсором мыши. А средствами игры вряд ли.

No it will be fine, feel free to change it. I'll be swapping it out for the next update anyway.

Did you do "Ready pre contact"?

Post a track

I was talking about a specific bug (effectively limiting the map to daytime operations) and you are talking about rebuilding a map.

I think everyone has the same plane where the tail wheel doesn’t swivel 360, but if you have good rudder pedals and are gentle with the inputs, along with some axis curves and tuning to tame the brakes a bit, then it’s not too difficult to taxi around and do nice S-turns down the taxiway. Also, back-taxiing on the carrier to the stern, then spinning around for takeoff is totally do-able even with the tail wheel swivel limited. Just takes a little practice and very gentle taps on the brakes. I’m sure this will get tuned eventually, as we also all have the same early-access module.

Ok will check that out first Regards

Different generations, but pretty obvious shared lineagenull

@_Hoss, I don't understand why some people don't have an issue while others, like myself, have the issue with diff braking in the Corsair. I confirmed the problem still persists after the Jul 23 update. @-Rudel-, do you have visibility on this issue?

A preview of a GCA/PAR script I have in development.

@BIGNEWY, this is becoming more and more frustrating. Can this problem be addressed, please? Can we get some further traction other than "Investigating"? I could avail myself for a Discord chat or other means to dialog about this long-standing issue. Here are more items to point out about the TEDAC display. 1. Spawned in first AH-64 in Pilot seat. 2. Autopilot Controls Indicator display blocked by black overlay. 3. Switched to CPG seat, didn't play with TEDAC. 4. Jumped back to Pilot seat, TEDAC display still on; Auotpilot Controls Indicator display blocked by TEDAC display. 5. Spawned in to new aircraft, CH-47F. Nothing unusual about the displays. 6. Spawned in to a second (different) AH-64 in Pilot seat. 7. TEDAC display still on from the first spawn! It was immediately present because the rest of the cockpit was still being rendered. Notice the blurry segments? First screenshot represents first spawn. This was taken after I moved from Pilot to CPG then back to Pilot seats. Note the Yellow Box showing the TEDAC overlay and the purple arrow shows the Autopilot Controls Indicator being blocked. Afterwards, I spawned into a CH-47, nothing unusual with the displays. Unless you count the Left MFD not being displayed. Lastly, I spawned into a different AH-64 slot, in the Pilot seat. While the cockpit was being rendered (see blurry segments), the TEDAC display remained on. That was 2 aircraft spawns ago! Why does the TEDAC display remain on after switching between 3 different aircraft slots?

I can talk to Candy about removing it if its no longer out there. It was really only for looks. Let me see if its no longer part of the link.

I haven't flown the Harrier in a while, but maybe you should try only holding down the pickle button once the cue appears at 5 secs? I have a hunch that you are pickling waaaay to early. I seem to remember something from somewhere saying 5 secs from release depress pickle. Give that a try?