Moonshine

t80 he said. dont have his track, ill ask him

buddy of mine said he had issues with hellfires fired at tanks not doing any damage. maybe unrelated or maybe something wrong with the tanks all together and not the weapon itself. probably worth checking both possibilities

Its the return of ground units. Best to be seen when putting the TGP in A-A mode, then lock one of those contacts with the A-A radar. Youll see in the pod what you locked.

seeing the same with the viper. not a single tank was dead or even severely damaged. CBU-97_damage.trk

the CCIP pipper is correcting for wind, you can notice it most when you add lots of crosswind. your pipper will be very far off the center of your HUD

Ive tested with and without. Doesnt make a difference. After the cleanup and repair plus me wiping my saved games folder i ran the game with pure game files, still happened

tried it with different amounts of fuel. while i cant seem to replicate it, i do feel like the nose drops 10-15kts earlier than previously. Landing_2xBag_8000lbs.trk Landing_2xBag_6000lbs.trk Landing_2xBag_3000lbs.trk

thanks for looking into it. ill completely wipe and fresh install over the upcoming days to see if that fixes it i dont get it since when opening the stm via text editor it all looks fine

Will do, thanks for your time edit: did a full repair, still the same, even created a completely fresh folder under saved games

i made a short recording showing it: https://drive.google.com/file/d/1u4tOgUk7MxP00Ko3mLVTX2n14J-v1NPY/view?usp=share_link in short, after saving the miz and creating the STM the number look like that (which is correct): however after loading the STM into a new empty mission, the numbers look like that: as you can see, 203 and 204 are swapped

Scenario; create a flight, 4 members, ascending STN numbers (as per default) Save the mission. Create Static Template Open new, empty mission Load static template Check STN - number 3 and 4 are switched. Seems like when generating the STN, something gets messed up. when checking the STN in a text editor, everything seems to be correct, however, upon loading it, the jets have the wrong values Test miz and STN file attached. edit; only tested with vipers, assume its the same for other aircraft too STN TEST.stm STN_TEST.miz

tested it, seems fine to me, see tracks attached. make sure you are not too low so the fins can actually open and slow the bomb down before it hits the ground and dont be too fast either otherwise the fins cant decelerate the bomb enough and surely dont be both Post-Designate-CCIP_MK82SE.trk Post-Designate-CCIP_MK82SE_3.trk Post-Designate-CCIP_MK82SE_2.trk

map problem, not aircraft; been reported for ages. makes some of the most interesting airfields on PG not very useable if ILS approaches are needed/wanted here some of the posts about it, there is many more in the PG bug report section

that makes no sense, the rail itself doesnt move at all. you boresight the missile seeker. you only have to do it once per station as it will share the BSGT data to the other missiles on the same station

Pods are fixed at the cheek stations. The only thing that gets stowed are the lenses of the tgp when putting it to standby or power off. (Not sure if the 3D model shows it or not)

it was twice listed as "fixed" in the patchnotes but never really was

There is a freeze option one could (and in this case should) use yes. No idea if the recentering of the crosshair is realistic on every sweep.

Yeah its funny, after the first fix you take, moving the tgp with the fix page open actally shows a decreasing offset the closer you get to your very initial steerpoint location. In my case it was the tower on the airfield. Deviation showed 0 the closer i got to that tower, even though the steerpoint diamond was at one end of the runway

taking a NAV-Fix with the TGP seems to not be putting the "updated" steerpoint location where i designated it using the same procedure as explained by wags here; <https://www.youtube.com/watch?v=RBHrEzLGSqw and here: https://forum.dcs.world/topic/209147-viper-mini-updates/?do=findComment&comment=4992813 OFLY works fine, HUD works fine and FCR works but is a pain as it constantly resets the crosshair during sweeps, having to start over Track attached, mission date 1980 to ensure GPS isnt available NAV-FIX_with_TGP_broken.trk

yeah they are still broken. been listed as fixed in two separate patches yet the issue remains. for both OAs, the symbology appears to be below ground. the higher you set the elevation data in the DED, the more "below ground" they appear. as if the values are in the negative. dont know why this thread has the "missing trackfile" tag still...

think these reports are related. JSOWs are pretty broken

Yeah same here. Very annoying.

that is true, and if its modelled in DCS as well then there is still something wrong with it as if it would use electro-optical tracker i should not get a launch warning either, similar to the HQ-7 and Rapier

as the title says: fly towards SA-8 -> you get lock and launch warning. defend the first missiles (usually 2). turn back into the SA-8 -> you will get missile launch warning but no lock-on warning prior to that. out of the encyclopedia the SA-8 is semi-active radar homing. if i understand that correctly, that should always give lock before launch warnings on RWR track attached. RWR_no-follow-up-lock-warning.trk

plane does roll right when a TGP is equipped as the TGP is on the right cheekstation. you can balance it out somewhat by also adding a HTS to the left cheekstation but its still not equal, so you will have to trim a little to the left. however it doesnt roll right when your jet has balanced loadouts (mostly when not having any pods at all) best way to try it out is a no wind mission (to avoid crosswind) and clean loadout. if the jet still rolls, then surely its not the planes fault