Benom8

It looks like this affects other airframes too. I'll change the title.

Hi, When occupying an F/A-18 on deck and switching to the new Airboss station, the cockpit and canopy of my airframe are not appearing. This is affecting singleplayer and multiplayer. Airboss F18 canopy bug.trk

My first impression is that the upgrade is fantastic. It's so much better without the pre-baked shadows. The matching between the rivers and satellite imagery feels better too (or maybe I'm imagining it). Note that this module sits at 96GB currently (on my system, at least). Looking forward to flying this map some more!

I solved this by clearing the "Thrust" axes on all affected modules, restarting DCS then re-creating the assignments. It may also work if you reassign the binding first, then restart. The restart seems to be the key.

In the changelog for the new Dynamic Spawn functionality, it is mentioned that the devs of MIST, MOOSE & CTLD are being consulted / supported to update their scripts. It's good to hear that these community projects are being taken into account, but will any changes or new scripting options be documented publicly in a timely manner too? At the servers I help with, we maintain our own scripting libraries and it would be nice not to miss out on new features or run into breaking changes for lack of documentation. Many thanks.

I also hope we get Masada added at some point. My understanding is that it's below sea level and the current DCS TDK (Terrain Development Kit) doesn't support that. This was previously discussed here:

The absence of a wishlist subforum is the real bug here

That might avoid the need to open the controls window and position your physical controls to match before turning off the AI. I was thinking that if the AI could force trim the helo before deactivating, and/or the option to have the control window open/close automatically with AI engagement would also help these problems.

"He who testeth twice, shall deploy but once." "Estimate not, lest ye be estimated." - Dev proverbs. Looking forward to the patch when it's ready

I am unable to bind the master arm switch and gun switch for the keyboard as either copilot or pilot. There are "Special For Joystick" bindings for these, but the basic keyboard ones seem to be missing (i.e. not bindable), unless I'm overlooking something.nullnull

Here's a track with a mild example of this on Nevada. (You need to break out of the recorded head movements and look accross at the CP/G screen). After slewing and zooming the MMS a bit, clouds appear in front of the scenery except in the top-left of the display. OH-58 MMS bug.trk

I saw this today on Caucasus, MP. It seemed to appear or dissapear when changing the FOV of the MMS.

I am hearing Slim Pickings for some reason... I was gifted one RB module and have the SA map (RB in name only, it seems), so I'm not so invested in these events. Still, "no man is an island" applies - all players and developers are losing out from this in some way. Pressure from the community on refunds etc. surely helps to keep minds focussed, but it seems that most of the hot air is outside the balloon at this point. Hoping that this all smoothes out in the fullness of time.

Looks like the image links are broken... I've seen some videos about this update though, and it looks good. Thanks @Raz_Specter (et al?) for keeping heads down on this project!

A repair (or perhaps just restarting DCS) has improved the issue - it's barely happening in the first track now. The radar is useable for BVR again. The behaviour can still be seen in the second track though (at least for me).

Here's another example on the Caucasus, I'm the only entity in the mission. F-4 Radar Lines 2.trk

Hi, I'm noticing that the radar sometimes only renders random vertical strips during a sweep, or even just vertical lines and no useful picture. This can happen whether it's Jester as WSO, or if I've switched to the back seat to try different settings. With an air start I see this pattern: a normal radar picture for a couple of sweeps, then Jester sets the gain too high for a sweep or two, then it's mostly black with bright vertical lines. There are possibly more lines when facing towards contacts (MiG-21s in this screenshot). I suspect this may be a bug (I don't remember it happening so much before the last patch), but maybe it's some real phenomenon (jamming 21s?? or hostile radars) I'm not accounting for. Not using the WIP radar special options (but the HB UI 30Hz mode is enabled). F-4 Radar Lines.trk

Yes, optional would be good (who knows what scripts people use that rely on pressing the keys a fixed number of times). Thanks I know about the f10 shortcut, but it's not really a workaround, as you need to find the target on the map and it also requires the use of the mouse, not just keyboard.

Hi, When cycling views with the f-keys, it's very easy to skip past the object you were looking for and have to go through all the objects again to find it again. It's also, for example, not possible to quickly return to the f1 view briefly between time spent spectating on an object, without cycling through all objects in that category again to find it each time. Any or all of the following changes/additional bindings for the f-keys would be very handy for quickly switching to the view you want: F-keys remember to the last selected object in that category, and switch back to it when changing category An additional binding to cycle backwards through a category A 'previous view' keybinding to step back through the last few categories and objects recently viewed. Thanks, Benom8 EDIT: I think the most glaring omission and least disruptive of the three to add is item 2. The others suggestions might need some more thought on the details, but something along those lines would be awesome.

I'm still looking forward to using this map more as it develops, but I can't say I'm too happy if this is the way it is going. It would be good to get confirmation of what the devs are planning in this regard, i.e. is this the final state of these areas? How widespread will these artifacts be? And finally, why?

@Flappie That's interesting! Thanks for working that out, and passing it on to the devs.

Hi all, Apologies for not checking in on this in a while, it seems like it's still happening (on my system at least). I've run a slow repair and with the attached track I get the following results: Mirrors on FPS Mirrors off FPS Mirrors hidden Threading Version 25 30 25 ST 2.8.6.41066 43-46 50-54 43-46 MT 2.8.6.41066 nullDCS settings attached. Mi24-Mirrors-FPS_2.trk

I've seen it several times before where a disembarking group does not include all units immediately. Upon the AI controller getting a task or maybe when the group starts moving, the remaining units appear in the group.

I also noticed the smoke disappears sometimes. Just checked and you're right, it seems to be toggling at the altitude it starts at. Thanks for figuring this out!

Being able to manually edit the .miz files to make certain modules optional to join a server is important to our group. Will this still check against only the requiredModules section in the miz file, or will editing that no-longer prevent users being blocked from joining?