key_stroked

I have the same issue in Multiplayer and reported it but accidentally put it in the main AH-64D forum. Can my thread be merged into this one please? https://forum.dcs.world/topic/346035-29351704-dcs-crashes-after-turning-on-vid-feed-in-left-mfd/#comment-5410359

I've provided a log and a trackfile. Is this being looked at?

https://www.reddit.com/r/hoggit/s/fiDzcejewa

It's always the first flight I do in the Apache per session in a multiplayer server. Track and log files attached. dcs.log SDCS_Syria2-20240327-222144.zip

That's one of the first things I did, and I explained that in the original post. It didn't work for me.

Let me check. ** Nope, still broken. Default view for the Apache is still set to 90 in SnapViews.lua, but hitting "Zoom Normal" defaults the camera FOV to 124.4 This screenshot was from today. I'm on the multi-thread executable version 2.9.2.49940

Yeah that's right. I don't know where the ED default view settings are, because SnapViewsDefault in the normal DCS directory only has the FC3 aircraft listed. I can't find the value of 124.4 anywhere. But yes, "default view" is getting completely ignored.

Yes, the zoom normal bind in every module.

Unfortunately, it didn't affect the Apache. So far, I haven't seen ED acknowledge that this is totally FUBAR now.

Are the green values min/max FOV? Are you suggesting to just set them to the same number? I also don't have a Server.lua file in that directory (same directory as SnapViews.lua). How am I supposed to generate that file?

Prior to the patch on 19.12.2023, the key assignment "Default Zoom" would correctly change the FOV setting to match the "{--default view" entry for any given aircraft in SnapViews.lua. After yesterday's patch, the default zoom is now 124.4 which basically turns the camera into a fish-eye lens and it's completely unplayable for me. I tested different values for the Apache in SnapViews.lua, but it won't use whatever value is set for the "default view" entry. As a test I set "90" for the default FOV in the Apache: But when I hit default zoom, it goes to 124.4. I've tried deleting SnapViews.lua from the Saved Games\DCS.openbeta\Config\View directory and let DCS rebuild it after saving a custom SnapView with no change. I've tried running a repair with no change. The issue of default zoom not resetting the FOV is a bug that has been around for several open beta versions. Before this latest patch, the workaround was to briefly select a snapview (windows key + numpad number) and then default zoom would work. Now, I'm just stuck with an FOV of 124.4 unless I manually change it with the "Zoom slow" keybinds, but you have to leave the console window open to get back to your desired FOV if you decide to zoom in or out at any point. Can this please be hot fixed?

Missed those. Thanks!

Ah interesting. Thanks.

CPG communications controls don't list anything labeled foot pedal. I thought the CPG foot pedals actually link to the control surfaces for flying from the front seat? I know the F-14 RIO pedals are setup for coms. Maybe you were thinking of those.

As far as I can tell, the TEDAC has no radio/ICS transmit buttons. In the real Apache, does the CPG have to let go of the TEDAC to find the radio HAT switch on the cyclic to use the radio or talk to the pilot over ICS? Seems like an oversight not to include radio controls on the thing the CPG would have his hands on the most, especially during combat. Or does the CPG just have a hot mic all the time?

Yes please

Well that's disappointing.

Then why does the store page and the in-game description still advertise hot start aircraft as a key feature? It's one of the reasons I bought this campaign.

Are we supposed to be able to choose between hot or cold starts? I just played missions 2 and 3, and it was a cold start for both of them. I prefer hot.

What priority was it on before?

Sold.

For what? They didn't fix anything yet.

Still can't see out of my canopy glass.

Sale pending.