Jump to content

Recommended Posts

Posted

Hello there. This bug report is a continuation of this discussion:
 


Namely, unlike a couple of years ago, the F-14A (i haven't tested the F-14B) seems to manifest increased performance (lift over drag) at higher mach numbers then it's supposed to, especially when compared to the CADC wing sweep schedule that is supposed to be optimized for maximum excess power. 

Right now, when wings are fully swept forward (20 degrees), the performance first drops at around mach 0.6, and then somehow raises at mach 0.7 and 0.8, before hitting a wall as expected near transonic speeds. I ran several tests, at different altitudes, and they all yield same results. I attach the video recordings from my tests with this post, as well as two short tracks taken this afternoon (i made them as short as possible) at mach 0.7 and 0.8 up at 15000ft. 

For full relevant documentation, please check the thread mentioned above.

The Videos:

 

 



And the tracks below:

https://drive.google.com/file/d/1-rbspHyUabuVm4sfsoq0805SjL0dOvpY/view?usp=sharing
https://drive.google.com/file/d/1FcdsbKbq6DGoN6d9z-kVMqeGdMH4QmXn/view?usp=sharing

Note, the tracks are too large for the 154kB restrictions (i wonder how short a track needs be to fit), so uploaded them to g-drive and given access to them. 

If needed, i can add the Tacview files as well. Have a great day and safe flying! 

  • Like 2

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

Posted
6 hours ago, captain_dalan said:

Note, the tracks are too large for the 154kB restrictions (i wonder how short a track needs be to fit)

It is probably your own limit based on the already uploaded attachments. You can delete some old ones in your profile to free the available space.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
On 10/23/2024 at 10:43 PM, draconus said:

It is probably your own limit based on the already uploaded attachments. You can delete some old ones in your profile to free the available space.

That's ok, i can afford to host these for the time being, hopefully until someone notices or investigates the thread. 

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

  • 1 month later...
Posted

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

  • 2 months later...
Posted

Bump

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

  • 2 months later...
Posted

@IronMike@Silhou
Routine bump! 

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

  • 1 month later...
Posted

I'm having over-sweep problems after landing, I can only move it to 68 and have to fiddle with lever that I use for wing sweep and only every 10th time it works

F-14, A-10CII, F/A-18, Spitfire, FC3, Supercarrier and all of the maps/terrains 

R7 5800X, 32GB DDR4 3733GHz CL14, RTX3090, Sound blaster Z, Oculus Quest 2 and Reverb G2, WINWING F/A-18 Orion HOTAS...

Posted (edited)
6 hours ago, Luka CMF said:

I'm having over-sweep problems after landing, I can only move it to 68 and have to fiddle with lever that I use for wing sweep and only every 10th time it works

This was reported as a problem when you use bound keys or axis other than mouse click and drag. 

Otherwise the procedure is this:

https://heatblur.se/F-14Manual/general.html#oversweep

Quote

To set the wings to oversweep the emergency wing-sweep handle should be moved to the 68° position and held in the extended position. This will deflate the wing-seal airbags and activate the horizontal tail authority system, indicated by the HZ TAIL AUTH caution light illuminating. When the HZ TAIL AUTH caution light goes out and the OVER flag on the wing-sweep indicator appears the oversweep interlocks are free and the handle can now be moved to the 75° position and stowed.

This has nothing to do with this thread though, please continue in your own thread.

Edited by draconus
  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
1 hour ago, draconus said:

This was reported as a problem when you use bound keys or axis other than mouse click and drag. 

Otherwise the procedure is this:

https://heatblur.se/F-14Manual/general.html#oversweep

This has nothing to do with this thread though, please continue in your own thread.

😢😢😢

F-14, A-10CII, F/A-18, Spitfire, FC3, Supercarrier and all of the maps/terrains 

R7 5800X, 32GB DDR4 3733GHz CL14, RTX3090, Sound blaster Z, Oculus Quest 2 and Reverb G2, WINWING F/A-18 Orion HOTAS...

Posted

It just can’t recreate locking you out until the bags deflate. If you find a tag for the bag state or the lock out you may be able to make your own physical “lock out” on your axis. It can’t move from 68° until the process is done, the jittering makes it think you moved it back forward from 68. 

The real one I think you have to go through a lock out gate past 68 and that’s when it deflates the bag with some proximity sensor in the lever mech in the lockout gate. 

gotta get creative. 

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...