In CCIP with LAU-3 selected the FCR is used to compute the slant range and impact solution even if it is OFF and not radiating. The same is happening with FCR in OVRD. [image: BHJy4iV.png]

@regev that has been already fixed in .5/.6.

@Quasi_Stellar That was the case! Thank you very much, problem solved!

@The_Fish - Yes. I think it’s a matter of Training to the new sight picture, but you could also be right about how BMS is boresighted. I’d been gunning in Hornet Trainers for a couple decades with great success and had some real trouble learning to strafe in the Viper - but once I figured it out I got it. i would imagine that the Viper and the Eagle would feel similar as far as knowing where your nose is wrt the cannon. …I had the same problem in the Harrier Trainer…further aggravated by the off-axis reaction of the recoil. Of all the Trainers I’ve flown, the Hornet has the easiest gun to use.

@lixus - this is a legitimate flaw.

TGP should not enter AREA track mode if the selected weapon is AGM-65G/L. Ref T.O. GR1F-16CJ-34-1-1 (1-223)

there is a more fundamental bug here, on the HAD itself. will be fixed for 4.38.

When DED is in MODE layer it is possible to change layer by pressing any of the ICP keys, the same as when in LIST layer

From CCRP attack mode set FCR override. Enter MARK function and perform slewing and designation. The aiming sensor is shown to be FCR even if FCR is in override mode (and in NO RAD) and shall not be used as sensor. [image: glIRswM.png]

After DTOS designation FCR AGR antenna is not commanded to measure the designated point but remains frozen on the last position before designation. In this condition the FCR is still shown as the sensor in use and the slant range is updated, even if the antenna is not pointing to the SPI. [image: pStBZxj.png]

In DTOS, FCR in AGR, antenna position is not commanded to the angle between TDBOX position and FCR boresight, but instead to the angle between TDBOX and FPM. DTOS (wrong) [image: UnTs8TX.png] CCIP (correct) [image: acwOaDh.png]

The FCR antenna in AGR has no gimbal limit and is allowed to go beyond -+60°. The image below shows the issue with elevation. Same behavior for azimuth. [image: Zbv69JJ.png]

PRE DESIGNATION [image: 7YPm7ra.png] POST DESIGNATION [image: OyIgwBH.png]

@airtex2019 Is the missing throttle axis repairable for the F/A-18? That would great if it was, appreciate it.

@airtex2019 It’s been a while that I did some SP in KTO, so I’ve to check.

@airtex2019 hi it isn’t hard to replicate, and even I can post a pic one cannot see the problem cause the jet will be invisible anyway. All you need is overcast condition, cloud tops at about FL150 ish (Current Korea weather can simulate that) and you fly above the cloud with the sun shining. Make your wingman or lead line abreast 2 miles (we did this not with AI) Sometimes it goes invisible sometimes not so I think it is probably related to the render engine choosing which light to cast.

@jayb New terrain = New assets… Forget anything you have in 4.37…

For the Latest Adobe Substance 3D Painter v.11 the plugin needs a new version in order to work. On Line 14 it must be changed from: from PySide2 import QtWidgets To: from PySide6 import QtWidgets DON’T DO THE FOLLOWING FOR PREVIOUS VERSIONS OF Adobe Substance 3D Painter. if someone wants to do it manually just edit with Notepad or Notepad++ the file bms-substance-exporter.py in C:\Users\YourUsername\Documents\Adobe\Adobe Substance 3D Painter\python\plugins Go to line 14 and make the change from 2 to 4 after PySide as stated above. Save the file. Open substance 3D Painter v.11 and it should work. if not Menu->Python->Reload Plugins Folder And u should be fine. DON’T DO THIS FOR PREVIOUS VERSIONS OF Adobe Substance 3D Painter.

Thank you all for your replies! I have managed to identify the problem and it is not related to a BMS bug after all. After the fresh installation I did yesterday, I found out that in addition to the previous ones, now I also lost “Engine external” and “sound effects” sounds at all… So, after several things I tried, I also tried to redirect the output sound from my 5.1 speakers to a different device (headset). And guest what? all sound could be heard… So, the problem was that different type of sounds are going to different sound channels (i.e Cockpit sounds goes to front speakers while RWR sounds goes to central speaker) and due to a button pressed in my 5.1 speakers, output was downgraded to stereo instead of 5.1. However, this did not work for BMS. And as it seems, in the two installations tried, different type of sounds were affected each time. Note that in Falcon AF and Falcon 4.0, nothing similar was happening. At both these installations, all sounds were going to front speakers, as stereo. When I configure again my speakers to 5.1 setting, all sounds came back also in these speakers. Thanks all of you again for your ideas and proposals.

@CallsignWombat check here… https://forum.falcon-bms.com/topic/28949/range-in-jhmcs?_=1741964898493