Khallimero

Never noticed it before. Maybe I'm not looking behind too often... Anyone knows the purpose of this ?

Hum...my bad. Here is a "real" picture. Looks like the "band" is missing from the external view only, and the internal view is correct (at least now, if it wasn't before)

Hello I'm flying the A-10C vanilla (not the A-10C II version, although that module is also installed), and I just noticed something in the middle-back of the canopy that looks like the beginning of the Scorpion helmet position sensor found on the A-10C II. Pretty sure that was not there before the december 2.7.9 patch. Moreover, it doesn't appear on the external views.

That's why you can (and should) change the desired impact angle in the weapon's profile, and it should work accordingly. That works for the GBU-38, but the GBU-54 doesn't care about it. At least it should use a less steep angle by default, so it wouldn't miss a stationnary target with the default value. F-16 and F-18 use 60° angle by default (edit : for GBU-38), and there is no issues with them (as far as I know).

Just feeling beeing ignored This looks like a serious issue to me. Here is another track where the bomb completely misses the target, due to its odd trajectory. (I strugled locking the target that time, but I wanted to be sure it was locked before droping the bomb) GBU-54-2.miz

At least at flight rotation speeds. This will prevent the shadows from flickering inside the cockpit (as seen below at 0:10)

Would be great if it becomes a native option in the game. At least for the cockpit view, to reduce the blade shadow flickering.

They should be grounded, it could damage the optics.

reported here :

Any value other than the default 0° seems to work. 60° is the default value for the F-16 (and maybe the F-18 too, if I remember correctly)

Maybe GBU-54s in GPS mode suffer the same issue. (sneaky topic update ) But as far as I tested, GBU-38s seemed to work fine once you changed the default 0° impact angle. Unlike GBU-54s.

erf, maybe already reported, on the second page, here : sorry...

Hello I may have found an issue with the laser maverick and its estimated flying time. The theroy is : after designating a target with the laser, the maverick locks on that point, and the TGP estimates the missile flying time. When the missile is fired, the countdown begins, and the laser automatically shuts off few seconds after it reaches 0, because the msiile should have reached the target. The problem is that when fired from long distance (7nm in the track I provide bellow), the missile lofts, and it takes longer to reach the target than the TGP estimated. And the laser shuts off before the missile reaches the target. This is not an issue with the laser overheating. The issue is in the estimated missile flying time. Laser maverick.trk

I tried to reproduce your results with the GBU-54. Looks like it also depends on when you release the bombs. If you release the GBU-54 as soon as you are in range, the bomb will not have enough energy to reach the vertical of the target, and it will actually hit the target with an angle smaller than 90°. But if you wait and drop the GBU-54 from the middle of the Dynamic Launch Zone (as I did in the track I provided with my first post), the bomb will go above the target, and then dive vertically. Regardless of the impact angle in the weapon profile.

Agreed. My first suggestion is only to make 60° the default value for the A-10, as it is for the F-18 and the F-16, instead of 0°. Agreed too. That's my second point. (strange, especially because it works fine for other GPS guided bombs)

Hello I've experienced some "issue" when using the GBU-54 as a JDAM (i.e. without laser designation), especially from high altitudes. As far as I have tested, the default impact angle (0, degree I guess) seems to ask the bomb to hit the target from above (= vertically). Because of the odd trajectory, it can make the bomb to go backward, and sometimes it even makes it to miss the target, Althought the "impact angle" weapon profile button tooltip says it has "no function", as for the GBU-38, it seems to work for the GBU-38, but not for the GBU-54. Attached is a track where I, from a high altitude : - first I drop a GBU-38 on a target, with the default 0° impact angle. You will notice the odd trajectory of the bomb. - then I change the impact angle to 45° in the weapon profile ; then I drop another GBU-38, the bomb trajectory looks good, with a 45° terminal angle. So it works fine. - then I drop a GBU-54 with the default settings (0° impact angle) ; the trajectory is the same as the first GBU-38, with a vertical terminal angle. - then I change the impact angle to 45° for the GBU-54 weapon profile ; the trajectory is the same as with a 0° impact angle. As a remediation, is it possble to : - make the default impact angle to 60° for all GPS-guided bombs, as for the F-16 JDAM, so it won't be necessary to change it before each flight - maybe edit the tooltip to say it works, at least for the GBU-38 - make the weapon profile impact angle configuration to work for the GBU-54 too ? (All tests done with the 2.7 stable release) Regards GBU-54.trk

Maybe with the new WW2 propellers technology used in 2.7, we may have a chance to get this. The flickering is very ... annoying.

Agreed. So what is this BS3 nonsense ?

What is that ? A Ka-50 with Ka-52 wings/pylons ? Never heard of that. Edit: erf, already a thread on that here : But again, I never saw a single-seat Ka-50 with 3 pylons on each wing. All were dual-seat Ka-52.

Hello Looks like AGM-154, when launched in PP mode with certain parameters (as far as I have tested : above 15000ft and 400mph), will "bounce" when it goes bellow a given altitude, and then will wander almost indefinitely. Bellow is a track illustrating that issue (I used "active pause" to speed up some parts). AGM-154 inf.trk

You seriously are working Sunday evening 9PM+ ? That is true dedication I guess. Good luck with the work then.

Hi I tried to record a track, I don't know why but the mouse cursor on the track does not show at the same position as in-game, so I guess a track is helpless. Luckyly, the issue is quite easy to repeat : make the TGP SOI in A/G mode, boat-switch aft to swicth to White-Hot display, put the mouse cursor over OSB-19 or OSB-20 to make the tooltip appear. Game is in English, Avionics language is English, OS is Win10 in English too. I have both A-10C and A-10C II modules installed (and some others too), the issue is the same with both. Regards

Found some "exotic" symbols in the TGP tooltips

Han... to me, it was more like a bottom heavy ball into a liquid filled sphere. So I expected it to don't drift at all. But as it actually requires electrical power to work, it must use some kind of gyroscopic effect. So it may drift over time. Note : I was talking about the SAI, not the ADI. (I guess I flew the A-10C too much these days)

After a quite long ferry flight (1+ hour), I just noticed that the ADI was slowly drifting, so that at one point it was completely upside down. Edit : oups, should have posted that under "bugs and problems". Don't know how to move it...