fjacobsen

Ah offcourse - thank You for the hint. I did read the notes, but missed it for JDAM's

Using GBU-38 or GBU-54 gives me no LAR range indicator on the HUD, at least when using pre-planned mode (Target points set on F10 map). I see the LAR rings on the EHSI and when releasing the JDAM's when within the LAR max and min rings, the boms do hit as intended. Is this a known bug ? (been some time since using the AV-8B).

It really seems that they aren´t very willing to fix this. It cannot be right that this hasn´t been fixed after such a long period.

You can have a close group of f.ex 4 targets, then use the TGP to make a MARK point on each target i.e MARK point A, B, C &D. In the profile You can set the MARK point A as target. Then You need to set the SPI on that target or just close to it, f.ex in the middleof that target group. Then drop a single bomb and it will hit the target under the MARK point A. Change the profile to the next MARK point f.ex B and reattack. The above works fine for me. I guess You can make serveral profiles, with each MARK point (A, B, C & D) and then select first profile, attack, select next profile, re-attack and so forth. If Your quicj on the fingers You might be able to do this in a quick succession and thus hit serveral targets in one pass, if they are all close to the SPI. Question is, if it is possible to give each bomb it´s own MARK point and then by dropping 4 bombs, hitting 4 targets in one attack run. This would still require the SPI to be near all targets.

It´s probably the standard FAC. Note that this is also for those who don´t have the old A-10C.

I think it´s the TGP that messes up the wewaypoints. When I use the TGP the waypoint positions and distance are messed up on the HUD, the HSD looks correct. Maybe it´s remnants from when the TGP manipulated the active waypoint to which it was slaved. I just flew a mission, practicing the AGM-88C HARM and flew without a TGP pod, HUD indications remained accurate.

Thanks BIGNEWY. I thought the ticket system was for bug reporting.

Has this changed with the 23rd Sep. 2020 update ?

As the title says... Despite it has been repprted for quite a while ago, nothing seems to have been fixed. According to the developer, the issue is on ED's side: https://forums.eagle.ru/showpost.php?p=4496974&postcount=41 How come nothing has been done by now - the module is unplayable, even on my high-end rig. I have send a ticket to ED, but history tells me that I shouldn´t have high hopes for other than generic replies.

I have now submitted an ticket to ED, though I have low expectations that this will help.

As title says.... How come ? We haven´t seen any updates to this for quite some time !!

With the 23rd September update I still get very low FPS with the Radar turned on - how come that this hasn't been fixed ? This module is still unplayable !!

It´s not the name on the package, but the content that matters :)

Stay calm and don´t expect too much, though a comprehensive update would be welcomed - wouldn´t be too early.

I´m looking forward to this. The A-10C is the most mature module of DCS and now becomes even better . Buying this is a no brainer for me.

Personally I will hold on buying more modules from Razbam until the M-2000C and AV-8B are in a state that can be deemed close to finished. I bought the M-2000C for almot 5 years ago, and it´s still not matured into release state. I bought the AV-8B for more than 3 years ago, and many features are still not in - so for me it´s still EA. Thats not a way to treat paying customers - EA rules or whatever is no excuse. If a module is out of EA, then all features promised should have been added, and only minor bugs present - thats not where we are with either of those two modules. It´s a real shame, cause both modules seems so promising, and acrually has some great features, but alot is still missing.

Any updates planned for today ?

Problem now is that initially the TD box on the HUD is set to the active steerpoint. If the steerpoint / TD box is within the field of view of the HUD, then You can slave it via the TGP. But if the active steerpoint is outside the HUD FOV, then it won´t slave and keeps staying at the steerpoint.

No track eiither... But I also see degrading FPS with the radar turned on. A few seconds after the radar is turned on, FPS dips from 80 to 20 FPS. After a while it returns to 80 FPS, but then periodically dips to 20. It seems more apperant flying at low altitudes, but there is no clear reason for why it happens.

Your explanation sounds right, but this is not how it works now. When TGP is SOI, the HUD Target box does not move to where You slew the TGP. ONLY if the the active steerpoint is within the HUD, it kind of works.

I wonder why the Channl map hasn´t been updated (as far as I can see in the changelogs) since the release. How hard is it to fix the ambient temperature bug ?

I doubt that it isn´t possible to to designate targets of opportunity with the Litening and have the HUD steering line guide You. Can some one, with RL knowledge, confirm that the real Litening / F-16 combo works like it does now ?

Yeah right now it seems that the active steerpoint has to be within the HUD FOV for the HUD TD box to move when the TGP is SOI and is slewed. I cannot believe that this is the way it worl IRL.

Sounds great- will report back once we got the update.

It can never be a solution to roll back driver. It seems this bug has been arounf for some month now. The devs should step up at fix this. Right now with my high-end PC it is literally unplayable with the rada turned on.