F18 bug BMS 4.33

[coolhands]

Hello
I have a graphic bug in F18 on panel engine

My PC
Windows 7
intel Core i5 4690K Cadencé à 3.50 GHz
16 Go de mémoire totale de type DDR3 à 1.07 GHz
NVIDIA GeForce GTX 970

https://www.youtube.com/watch?v=GrW9JBo44wI

[WaveyDave]

Which variant?

Is it repeatable.

Any special steps needed to repeat?

Any other mods installed?

Regards
Dave

[EL_JEFE32]

Same issue with the Balkans campaign that cool hand has.
F18c
Happens every time
No special steps
No other mods
Doesn’t affect me just figured I’d answer your questions that you asked him from another perspective.

[Daisan]

Also with F/A-18A here. Installed from scratch.

[Agave_Blue]

Same or similar on F18D/E in stock Korea.

Nothing required to reproduce. Just commit to ramp and/or ramp start and it should be there.

[WaveyDave]

Which exe 32/64bit ?

Regards
Dave

[Agave_Blue]

64 bit for mine. System specs in signature.

You can see it in this Ramp Start vid at ~2:00 (maybe elsewhere also): https://youtu.be/lVxky3d9mwc?t=2m

Edit:

If it’s convenient, while you’re looking at that, there is another ‘graphical anomaly’ in the F/A-18E (?and D) as well. See: https://youtu.be/lVxky3d9mwc?t=16s.

Again, happens consistently on ramp start.

[WaveyDave]

Do these problems only happen when doing a ramp start? What happens if you start from taxi or takeoff?

Regards
Dave

[Agave_Blue]

@WaveyDave:

Do these problems only happen when doing a ramp start? What happens if you start from taxi or takeoff?

Regards
Dave

For my post #7, yes …. Ramp, Taxi, Runway and airborne start are all the same.

Thanks for your consideration on this. About the most fun I ever had in the Falcon4 family was Hornet3.0.

[WaveyDave]

I’m trying to figure out what you guys are doing different to this:

Falcon BMS 4.33 - A/A refuel attempt in F/A-18 and fun – 08:01
— Callsign: Squeak

Any idea to help me narrow down the problem.

Regards
Dave

[coolhands]

F18c
Happens every time
No special steps
No other mods
64 and 32 bits same problem

[WaveyDave]

@coolhands:

F18c

In your original video it appears to not be in full screen mode, is that correct and have you tried it in full screen mode.

Regards
Dave

[coolhands]

Same problem in full screen mode

[WaveyDave]

Any ideas what you might be doing different to the other videos?

I’m not trying to be difficult about it but something must be making this happen and it’s never been seen before now.

From what I can tell it’s not a model issue otherwise everyone would have it, it could be code but then I need to know how to make it happen.

Regards
Dave

[StenneG]

Hej,
Same problem here…

Trying to help and find the problem…

1. Uninstalled BMS and cleaned registry with CCleaner/Auslogic Boostspeed
2. Fresh clean install of BMS.
3. NO SETTINGS CHANGED!
4. Testing whit training mission: Taxiway > Training mission carriertakeoff.
5. I restart BMS between all changes.

No problems so far…

Starting to apply settings and controls.
Restarting BMS between all tests.

1. Removed patch Play Intro Movie on Start Up. Working
2. New user. Working
3. in game Graphics: Applied multisampling and level 7. Working
4. AMD settings: application controlled. Working

Controllers:
1. Set afterburner. Working

Flight control:
1. Throttle Axis: X-axis Saitek x-55 throttle. Working

Avionics Control
1. Radar Antenna Elevation: X-rotation Saitek x-55 throttle. Working
2. Range Knob: Z-Axis Saitek x-55 throttle. Working
3. HUD Brightness: Z- rotation Saitek x-55 throttle. Working
4. HMS Brightness Y-rotation Saitek x-55 throttle. Working

Keyfile: BMS - Full.key
1. Applied my keyfile: StenneG_DX_Full.key. Working

No problems so far….
Now I am back to where the bug showed up with my previous BMS install… But no bug in sight???

… Exept making TE missions.

New TE mission: (Test_carrier)
Enterprise with one flight (F-18 E). Weather to problematistic, comms to carrier 16

Loadading my new TE mission…

Takeoff with full afterburner… Look att the readings. 07 07. Should read 100 100. Something wrong here.

Sorry, not the same bug, but a maybe on something here?

Back to training mission: Taxiway > Training mission carrier takeoff. Everything is fine. No bug in sight.

Hope this could help a little bit to take the matter further and solve the mysterious bug.

StenneG

PC Spec:
Windows 10 Pro 64-bit
ASUS P8 Z77-V
Intel Core i5-3570K CPU @ 3.40GHz
AMD Radeon HD Gigabyte 7870
AMD driver amd-catalyst-15.7.1-win10-64bit
Saitek x55

[WaveyDave]

FA-18E/F are not really supported. The cockpit has only been tested thoroughly in legacy hornets.

I will look to see if there is anything I can do to fix the Super Hornets but as I say they were not really the focus of the testing effort.

Sorry if this wasn’t made clear, Legacy Hornets only.

Regards
Dave

[StenneG]

Hej, again.

Could recreate the bug! Testing whit training mission: Taxiway > Training mission carriertakeoff.

It appears when enabling Smart Scaling.

Disable smart scaling and the bug is gone.

But the 07 07 remains in self made TE missions (F18E)

#################################
Now, when I slept on it. I remember that there was nothing wrong with the engine panel in my first installation of BMS 4:33, from the beginning.
The error first appeared after some time, thought no more of it then.

Smart Scaling I turned on a few days after the installation of BMS.
Around the same time started the engine panel display incorrect data, as I said, I thought no more about it then.

Forgot to test Smart Scaling above, sorry.

Thanks! For all the work you put into BMS, especially Carrier Ops

Regards StenneG

[WaveyDave]

Hi,

Thanks StenneG, I will check the Smart Scaling to see if that is causing the issue. Could be a code issue rather than a model issue.

Regarding the F18E, I checked the cockpit data files and can confirm there is an issue there that will impact on the cockpits functionality.

Regards
Dave

[Daisan]

I do confirm. Problem solved unchecking smart scalling!

Good one!

Thank you!

[jross]

[Waveydave],

Feeling your pain. Spent HOURS on this lately. Boom AR (F16) isn’t a big deal. This Boom-Vs-Probe thing though had me in a lather too. Most consistent results come from:

After clearance Pre-Contact Posn, turn OFF cockpit (“1” key) and fly using the lights in HUD only view. Once you get the F/A & U/D lights quiet, hold it there for a few seconds while the boomer stabs you. Then keep holding it. As your video mentions, not only are the lights harder to see (no matter the airframe) but, it seems, in the Hornet (and Harrier & Tornado) you can’t see them at all when you are in the correct position due to the canopy bow. So, this way, with the obstructions removed, it turns into ‘normal’ boom refueling.

NOTE: I don’t have the TrackIR gizmo that allows your head to translate left/right/fwd/back.

PS: And it feels to me as though the Hornet (and others), probably/possibly due to the FM’s, accelerate a bit quicker, thus making small throttle adjustments more difficult.