vCSG3 Bloat 203

happens to me with X52 and Orion (separately, 1 connected at a time). Hot spawns in the Hornet are fun with the sync function on... bit of a pain to have that option off... wonder if this has anything to do with AI tankers flying with full surface deflections in a straight line... maybe the default positions have been flipped somehow...?

hi again - please find a sample track. All players designated WP 2 as steerpoint 1 and WPDSG WP1 as target area, for each of their SLAM-ERs. Only Bloat's weapons are actually following the route in the track, the rest is recorded on my track as heading straight for the target. One exception - one of Knuckles' missiles was not designated correctly and went super-long - disregard. https://drive.google.com/file/d/1n7nxXEr9tocKAaFz_PMo-_a5e8R3C1H-/view?usp=sharing In reality, all missiles went to their assigned steerpoint and allowed terminal guidance at the correct time, and targets were hit using MITL, at the expected arrival times. sample map view:

@[ED]Obithis is not only a SLAM-ER behaviour, if you shoot harpoons out, you will only be able to observe your own harpoons home in on a ship, while your wingman's harpoons (on your own F6 view) will just fly the assigned heading and never appear to home in on the target). However, the hits get registered just fine for all players, as each player sees their own munitions fly to the correct target.

I can confirm this is happening consistently every time. Similarly, since 2.7, dropping a CCIP SnakeEye using the hornet - only the dropping pilot can see the correct RET setting and trajectory. Other pilots see the bomb follow a different (usually RET mode) trajectory on F6 and F10 views.

you are a legend - thank you @dimitriov

thank you - it definitely is wiping TOO mission coords from all stations & weapons, when undesignating.

hey folks, read up for the workaround - move your SCS to another DDI and you're good to go!

I appreciate you @[ED]Obi do you know if the part with jumpy snowplough is in this fix, by any chance?

Just to add, this is the same with ATFLIR. possible workaround: Seemingly, if it fails to WPDSG, but you then unbox TGT on the HSI, then WPDSG again, it tends to work...

When selecting a 0AGL waypoint as WPDSG, Litening will will not slew to the WP. It seems to be related to the zoom levels, as sometimes it works on the first attempt, but once zoomed in/out, it does not. Screenshots depict WP 1 selected: and subsequent WPDSG ground stabilises the pod wherever it was looking (as if TDC depressed): Attached is a short track that demonstrates the inability to slew the pod into the correct waypoint. We can also see visible stutter on the zoomed in image, which no longer floats at the same pace as the plane, when in snowplough mode. WPDSG bug.trk

I don't think there is a list, but I think previously it was crater texture replacement... could be more now

same here I'm afraid. someoen on ED Discord said one of the vehicles has been added to stock...? >Adds some stuff that's redundant with the 2.7.1 additions (PT-76, VAB MEPHISTO)

many thanks! good to know!

good to know!

hehe, good shout!

@Taz1004I'm a great fan of your work - thank you for continuous updates! If I may comment on the wavy motion of smoke in v12 - it's a great idea, but it feels a little bit exaggerated - is there any way to tune it down, or is there a limitation on what it can be?

I applaud your devotion to realism - ATFLIR is so inferior to the Litening right now, I can't bring myself to using it - I'd rather pretend I'm flying in a Marine Corps squadron :<

This thread's OP is correct. The Litening POD used to display a diamond in the centre of the reticle after TDC depress pre 2.7. Currently, this behaviour only shows when WPDSG a target. Upon slewing the pod and TDC depressing, the diamond is no longer displayed on the pod's screen, but is correctly sent to the aircraft's weapon systems and actually designated. The only change in 2.7 is the lack of a persistent diamond in the pod's screen. Whether that is correctly modelled now, or pre-2.7 - I don't know.

We just updated to today's version and have the following observations from VR: daylight and max brightness settings are not producing any glare in VR - they change hue slightly. This applies to DDIs, HUD and HMD, as seen in the screenshot.

Hi @BIGNEWY - thank you for looking at this. I'm attaching a short track illustrating the issue, and screenshot of two DDIs (one in night mode and one in day mode, max BRT each). I'm also attaching a track file from a random multiplayer server at night. Before 2.7, the day setting used at night would correctly almost blind you, and the night setting would be very prominent and, on occasion, even too bright, requiring a small tweak down on the BRT knob. Currently, the night setting is just about bright enough to read, but can't be tweaked up. This is exacerbated in VR, where the difference between night and day mode is extremely small and DDIs are difficult to read. I will attach screenshots of VR once I get them from squadmates. Track link: https://drive.google.com/file/d/1jZhxrgkYbheOyhsyLd0bI9b6KvdT_WUA/view?usp=sharing

thank you for your tireless work - amazing! For clarification, the SP version is basically the non-IC version, right? It does add a few more effects than the MP version, just like before...?

It would be fantastic to have the ability to implement mods using the database. We were really enjoying our callsigns mod until 2.7... :<

lovely as ever and no issues in 2.7 - except for a friend in VR, who's having black outlines for all CCS trees. Just thought I'd bring it up on your radar @Taz1004 - it might not be related to your mod specifically...

This definitely started happening only after GBU-24 was introduced and there is no rhyme or reason and hence it's, so far, irreproducible. In the other thread, I posted a track and a tacview with some more details of it happening to two pilots on PG, within minutes of one another: We are experiencing way more crashes still when releasing bombs, as well as during setting their parameters using the UFC OSB - this applies to other bombs, not just LGBs, but can be unrelated. I saw two patch note changelogs mentioning a line that sounds like an attempt to fix this, but it still happens on occasion.

yes, linear distance covered probably closer to 400nm