CajunJosh

They certainly don't appear to be as effective as they used to. Is it possible this is related to poor splash damage modeling? It would make sense if the harm were to explode right over the target potentially causing damage to the sensitive equipment but since disabling vs destroying units isn't modeled in DCS is this real world behavior rendering them less effective in the DCS environment?

So today in the open beta I see the BRM1 guided rockets have been updated and I assume are using the same logic as the A10C II's APKWS. Just wondering if one of the devs can chime in and tell us what's now different on the back in and what, if any changes we might expect out of the behavior on the deployment side of things.

Today I was able to get CCRP bombing to work for a brief period of time by setting the target airfield coordinates at a steer point right before takeoff. Once I got in the area I had to place the aircraft in NAV mode, select the TGP, select A-G mode and only then could I go into A2G and have it work. At some point I accidentally hit TMS down which I assume doubles at courser zero. From that point forward nothing I did on the TGP had any impact on the HUD. Never got the HUD pointers directing me to the drop point and the bomb drop line for the CBU-97's kept directing me towards the steer point.

I haven't flown the Viper since right around the initial release. At that time the TGP seemed excessively buggy. Now almost one year later it seems nothing has changed. Is this consistent with actual TGP behavior in the Viper or have bugs been introduced recently/never been fixed? When I fly the F18, JF17, AV88B or A10C they all seem to operate in pretty much the same way. 1.) Set the system to CCRP. 2.) SOI the TGP. 3.) Locate hostile and designate them as a target with the targeting pod. 4.) Transfer attention to the HUD to be directed to the fly over/release point for the weapon. 5.) Release weapon. Is the F16 just that drastically different from every other module in DCS or is the TGP completely bugged? Can I just manually set some random way point before taking off to have the system work properly?

The numbers are definitely much lower now than easily searchable WW2 era testing documents.

When flying straight and level and properly trimmed on the deck I used to get just below 350 MPH with throttle, turbo and prop RPM all locked together at maximum. Now when I fly with cowling closed, gear up, flaps up and allow the engine and oil temps to warp up to the blue range before T/O I'm seeing anywhere from 260 to 300 MPH under the same conditions.

When connecting to MP servers my SRS no longer sees the P47 radio. Radio works fine on same severs when using p51 or FW190D9. dcs.log

It does seem odd that I can fly with my canopy open or closed in formation and I can hear the sound of other P47s flying off in the distance louder than my own.

Having the same issue.

Anyone else having trouble with their P47 getting above 260 MPH now?

Using the Samsung Odyssey+ on the latest open beta version. During the day everything is normal but at night whenever I move my head I notice significant motion blur on the edges of any contracting objects like the cockpit canopy and frame or water along a shoreline. It's been a while since I've flown at night but I don't recall ever seeing this before.

Good to see the WIP in progress is up to the point where it can fly and looks decent. Look forward to startup and systems familiarization videos as work progresses. Wondering if it's far enough along to make a debut in 2020 or if we will more than likely see her in 2021. Either way, looks to be a nice addition.

This is what it used to look like when you had a target selected with the TPOD. Now the drop path is completely random and often times not even in the same direction the aircraft is heading.

Is anyone else having trouble with the distance to drop bombs indicator not showing up in the HSD? I select a weapon like the sensor fused glide bomb. Set the bomb to target of opportunity. I love over to the tpod and lock a target but get a dotted line on my HSD in a completely different direction then the target. It used to draw a path to the target and go solid when it was time to drop as well as display a perpendicular line showing how far you were to weapon release. Has something changed or is this just a bug?

What's the battery time on the LD-10? Or is it the same?

Ditto Ditto Ditto Direct evidence of the lights brightness below. Even if it's a later variant of the hornet I'm sure the technology in a xenon strobe light hasn't changed much. I sure hope they bother looking at this thread and consider making the necessary changes. The F18's formation lights are looking much better and the cockpit lighting is great but this light looks horrible. The F5's light looks much closer to what I would expect with the F18.

Does anyone have any idea how close the waypoint has to be to the actual radar to get the LD10 to change course once it gets in the area. It seems like if your way point is more than a mile or two off you have no luck. Was wondering if there is a way to maybe tweak altitude on the waypoint to make the missile start looking for an emitter at a higher altitude.

I've been flying it low and slow at a low of ground targets and this thing really seems to think it's a Viggen. Dodging SAMS and getting in to strike an EWRs with guns before getting out. My big hang up has been trying to shoot a specific radar when the LD10 in passive mode typically wants to head straight into the nearest SD10 radar as it has the strongest signal/highest threat. I tried setting a PP point which does show up in nav mode but the LD10 wouldn't track to that area when fired in active mode. I will now try using WPT points instead and see if this works. If it does it will be enough missile control discretion for me.

So am I correct in what I'm interpreting here? Data Line #40 is used for your current SPI. If no SPI is set via radar or TPOD then line 40 will populate with your current selected way point? I'm wondering if I can set a PP point on the F10 may say PP1. Then set my flight plane to point 36 (PP1) then fire off an LD10 in ACT mode which in theory would track to the PP point since that would be populating line 40. Am I completely wrong on this? Right now the LD10's seem like great weapons but don't offer any where near the discretion you get with the F18's harms.

This issue appears to be resolved after the latest patch and INS updates.

+1

Yes however I receive no shoot que all the way down to less that 1nm from the target.

When using the BRM-1 guided rockets in VR I don't get the in range que on the hud within the 4.5m engagement range. I've tried following the Chuck's Guide startup procedure but that doesn't seem to help. The pod is lasing properly as the rockets will track and hit the target point but I never get the que even afterr closing to well below the 4.5m range. I did a fresh install of the module with a hot started aircraft already in the air and it started working but when I went into a multi player server after restarting DCS I get nothing.

Is this still broken because I'm having similar issues whether in SP or MP where I can't see the TGP pointer on the HUD?

Sad to hear about he AH-1 but appreciate the transparency.