Hey everyone,hope you are all enjoying flying right now.
I want to start a campaign on the Balkan theater with the F104S does anyone have a tutorial or suggestions for it? I’m having troubles using the AIM-7 sparrow
Thank you in advance for the help

@AWmk1 said in A10 flight model:

@Mav-jp of course, I completely understand - my question is just open to anyone:
is this hard pitch up/down while crossing a certain speed remotely based in reality, or completely a bug?

this can’t be real, this is a problem in the modeling

@razo It’s cut off because I have “HUD NAV mode ALT and SPD tapes lag” enabled. They follow the FPV in pitch when in NAV mode with the landing gear down.

Here is a picture of the HUD in flight:

alt text

unfortunately… Noty much we can do about old models…

@Mav-jp Indeed, I play with some values and see no notable difference . Its all on the FLCS hard coded which I have no power to change with excel…

Nevertheless some values are kind of off like inertia on all axes and indeed I see they affect the fm ,
also area2span ?

There is a laser code, and an LST code - make sure you have the LST code set correctly via the DED, and that the LST is searching in the expected area of the spot.

@airtex2019 Yes, now that is clear that things what I looking for, is not for public. Hmm, then that is what it is now. I didn’t look into it but I guess the Tornado flight model is based on the Flight Manuals of the Italian variants, which are available to the public.
Thanks the answer anyway!

@w1nwho

You need to use the editor to change the weapon loadouts for aircraft. You can access the editor from the Falcon BMS.

Gentlemen,

I’m currently refurbishing an older 3D cockpit for BMS and encountered the problem that the MFDs, RWR, DED and PFL defined within the 3dckpit.dat are floating when 6DOF movements are applied. The displays are properly aligned from the cockpit eye reference point of no 6DOF movements are applied. I figured that the 6DOF coordinates (first 9 values) in the 3dckpit dat are zeroed out in other dat files. Applying this made the displays disappear. By adjusting the remaining 4 values which define the X and Y coordinates for these displays (top, bottom, left, right) I managed to get the, now non-floating, displays back into the cockpit FOV. Unfortunately a perfect alignment isn’t possible as displays are cut off, if they leave certain boundaries. That led me to the conclusion that the mapping area to which the displays are rendered is insufficient. Altering the entire cockpit model’s position with the Lod Editor allows for a good alignment of some, but not all displays and is certainly not addressing the root cause.

My question is, how can this mapping area be redefined to match the cockpit model? Is it possi le with LE and if yes, how?

Thanks in advance

Good Day, All,
Here’s a current update: In your jet’s afm file, HAS NASA has to be 2.

Hi Scorpion is possible to add your Typhoon 3d model in BMS 4.34 Balkans theatre?

Is the drag of a store on a specific pylon part planned to be implemented? I.e. fitting an AMRAAM to station 1 adds a DI of 3 and fitting it to station 4 adds a DI of 4.

<p>Hi, Guys. Aragorn, I’m not sure if that’s our work or not, but yes we do cockpit textures. <br />Seifer, that’s great that the Dev’s got the stuff, and thanks for including it! So, 4.36 won’t have the hotspot issues as when 4.35 came out.</p>

@Dee-Jay:

You shouldn’t do that because the GD-53 is derivated from the AN/APG/67 and are extremely similar if not almost identical.
So it is normal to have the same symbol. Doing what you want to do is a kind of “cheat”.

Do the AI use the RWR to help discriminate friendlies from foes when they don’t have any other mean, or do they cheat too?

@smartaxe:

Thank you!
Oh boy. I had tunnel vision on this issue, or as pilots might say, “target infatuation”.

Just because TypeAC 9 DiD make a plane (like the f8 I’m playing with) carrier/launch bar capable. That’s not the only factor.
I see now f14a is “6” and it works too!

Did you fix these in U1?

Because I tested a while back and ctd was produced unless I changed F14s to TypeAC 9.

Now it’s working fine as type 6 or 7.
Soooo. Time to start winmerge checks.

Btw this info just introduced a fix to the f8 wing issue.
Now just have to try tweaking some more on fm/afm.

Thanks for the help even if it wasn’t default kto issues.

the launchbar issues have been solved in U1 IIRC

Again there is no relation between typeAC and lauchbar 🙂

That helped me a lot,thx buff 🙂