Gierasimov

"After the upcoming release we will continue integrating the new landing gear physics into other aircraft, both WWII and modern". First of all it is going to take years before it comes to Fulcrum is at all, I would imagine other aircraft means the latest tech - Hornet & Viper, maybe Hog, also would think Hind and AH-64D, maybe upcoming Chinook (?) I doubt it will be invested in FC3 Fulcrum maybe if ED goes ahead with the new module, it would be awesome...

Plot twist, ED secretly released MAC together with BVR Productions and Baltic Dragon is going to voice Jester 3.0 with Iceman being Jell-O Seriously though, MAC could be anything right now, in development, on-hold, name changed, evolved into an elaborate asset pack (the new 3D models discussion...). They will let us know once there is something to say.

That crew FLIR screenshot shows the pilot.. is it going to be added as a static at some point?

Ah. Got you! Well at least ED knows about it and hopefully they are going to find the fix, at some point.

Hi, DCS 2.9.0.47168 Open Beta -- mentions only one known issue: Added New pilot model from first person (Work in progress). Known issues: The salute command doesn't work when using option Afterburner detent. However, another one is the kneeboard that seems to skip on displaying pages from the or the information brought by the past update (DCS 2.7.14.23966 Open Beta): Added Additional carrier data to the kneeboard - ATC frequency, TACAN and ILCS channel.

Thank you!

Does anybody at ED know what's that supposed to mean? @BIGNEWY

I was going nuts with this one. Why I can't get the gun in HUD. Turns out the gun is pretty useless in A/G in it's current form.

@ianick hey can you confirm if it is flickering for you in single threaded version in latest beta? For me it is only the multithreading version where I observe this issue.

Thanks, same here, I tried in MT have not tried in ST yet, was working fine in two beta versions back for sure, but I am not certain when exactly it stopped as I was flying without screens in-between patches.

@ianick - I also experience the same effect now. Moved to MSI 4080 and my vsync is off, nvidia is set to use application preference. Did you resolve your issue?

@BIGNEWY hello sir, Are there any plans to make it possible to select active runway in ME at all? With the new maps specifically it is now evident that active runways configured by developers are not optimal or outright wrong. Syria, Sinai, but also Persian Gulf and NTTR, and I suspect other maps too, limit what can be achieved when mission building. Thanks.

Thanks @Backy 51 , also it makes me think it was fully intentional, as even the radio is calling SPX and not CW. That's a bummer, especially for those who would like to build a mission with that airbase.

Hi @OnReTech - I want to bring to your attention, what I think is a bug. Cairo West AB in DCS is where Sphinx International Airport is in real life, therefore AI takes long minutes to taxi from actual AB to runway at SPX and returns to the wrong runway as well. Since we don't have the civilian traffic in DCS and it is D COMBAT S, I think Cairo West should sit where it is in real life and not replace SPX as it was implemented. null

Nice one, let's hope the team effort can make your project even better! All the best!

Seems that AI E7 coming with Aussie map

I purchased for myself and for a friend. So the equilibrium prevails yet again

EA 072023 The image posted and Combat Aircraft calendar seem to suggest July

Brings back memories for sure ! Thank you !

I was away from Discord recently. If they are working on a fix then that's that. I fixed my skins, I get to take nice screenshots. Cool.

Well, this is not a bug. Just saying. Quick look at the Hornet as an example. ALL default skins that were included in the module work fine. So, ED changed the way how liveries work (by changing description.lua and under the hood code) AND they ensured that default liveries work as well, which means it is not 'by mistake'. Word 'acknowledged' tagged to this thread simply means that ED is aware of what was posted, which might as well as might not mean that they are going to 'fix' it. In the past we had several examples of ED backing out or partially reverting changes that were not that good, but this one, well, it makes controlling the liveries much easier with much less lines to write in Lua to have the livery working exactly as needed, so to me this is welcomed change and I like it, just don't really liked the way how it was introduced out of the sudden without anything being said, commented or explained... However this style is also known.

I honestly don't expect this to be "fixed" by ED. Looking and description.lua files it seems it is not a mistake, but rather a new method. I mean, the change in the file structure must have been accompanied by the code side of things. It does not look like a "let's fix a typo in the line of code". Changing the lua files for skins is actually not that hard. It might prove time consuming to some, but its something that we can fix ourselves. I posted my "solution" here is anyone's interested:

I knew it would turn out like this. Case closed I guess.