Jump to content

Recommended Posts

Posted

I did some additional tweaking on the dry thrust values.

Final results:

Mach 1.209 @ 80 feet max speed.   Mach 1.028 @ 80 feet super cruise.

Mach 2.272 @ 50k feet max speed.  Mach 1.830 @ 50k feet super cruise.  

From the Wiki:  Lockheed Martin F-22 Raptor - Wikipedia

  • Mach 2.25 (1,500 mph, 2,414 km/h) at altitude
    • Mach 1.21, 800 knots (921 mph; 1,482 km/h) at sea level
    • Mach 1.82 (1,220 mph, 1,963 km/h) supercruise at altitude

That puts all Mach numbers within 1% of publicly reported values with all specs the same as public values.

Single player version updated.

  • Like 1
  • Thanks 1
Posted (edited)

Silly question, but how do you control the radar antenna elevation when using the enhancement mod ?...

I can control the default Grinnelli F-22A radars elevation ok using either the OSB 18 or OSB 20 buttons on the center MFD. 

However since i have installed the "enhancment" mod ...... pressing the OSB 20 button causes the antenna elevation to go fully up..... and pressing the OSB 18 button causes the antenna to go fully down...... nothing in between 

I have deleted all axis/bindings so there should be no other control conflicts...

Any guidance much appreciated .... thanks. 

Edited by Gunnergolly

Win 11 Home 64Bit, i7-13700K@5.2Ghz Water Cooled, 32 Gb RAM, PNY RTX4090, Pimax Crystal, Quest Pro, Realsimulator FSSB R3 ULTRA, Virpil/Thrustmaster Warthog HOTAS combo, MFG Crosswind Pedals.

Posted
5 hours ago, Gunnergolly said:

Silly question, but how do you control the radar antenna elevation when using the enhancement mod ?...

I can control the default Grinnelli F-22A radars elevation ok using either the OSB 18 or OSB 20 buttons on the center MFD. 

However since i have installed the "enhancment" mod ...... pressing the OSB 20 button causes the antenna elevation to go fully up..... and pressing the OSB 18 button causes the antenna to go fully down...... nothing in between 

I have deleted all axis/bindings so there should be no other control conflicts...

Any guidance much appreciated .... thanks. 

 

There are three buttons now on the upper left the middle one has a "-" next to it and it represents "STOP".

It's a bit of a pain, but you start to move the elevation and you hit stop quickly before they transit all the way up or down.

This was a side effect of decrypting and rebuilding the PMFD.lua system file and not being provided a decrypted copy of it.  I have a decrypted copy of the MFD.lua but not for the center PMFD.  I did the best I could to reconstruct it and add the features I wanted.  Lost a couple of things along the way but I felt the gains were worth it.

I did contact GD and ask him about access to the file, but I received no response.

  • Thanks 1
Posted

Check the 8 min mark.  He talks about the Raptors sustained turn rate being 28 degrees/second @ 20k feet.

I have TacView but have some issues getting it work properly.  If anyone else has the ability, I'd love to know what the TRT (degrees per second turn rate) and the TRD (Turn radius) are with the updated custom flight model version of the lua are.

I know that with the accurate wing area it seems to turn a very tight circle (low radius) pretty quickly at around 150kts.  And as long as you don't over-rudder or pull too hard above 30 AoA it will do that all day long, or until you run out of gas.

Posted
17 minutes ago, Nightstorm said:

There are three buttons now on the upper left the middle one has a "-" next to it and it represents "STOP".

It's a bit of a pain, but you start to move the elevation and you hit stop quickly before they transit all the way up or down.

This was a side effect of decrypting and rebuilding the PMFD.lua system file and not being provided a decrypted copy of it.  I have a decrypted copy of the MFD.lua but not for the center PMFD.  I did the best I could to reconstruct it and add the features I wanted.  Lost a couple of things along the way but I felt the gains were worth it.

I did contact GD and ask him about access to the file, but I received no response.

If this function is put on the joystick, then the movement is controlled and smooth.

Posted
Just now, RaptorFighter said:

If this function is put on the joystick, then the movement is controlled and smooth.

Did I already set up joystick controls for that?  I can't recall.  If I didn't, I can look at that.  Seems like a great way to control it with a hat switch or something.

Posted (edited)
9 minutes ago, Nightstorm said:

Did I already set up joystick controls for that?  I can't recall.  If I didn't, I can look at that.  Seems like a great way to control it with a hat switch or something.

I have this function on the joystick works fine:-)

Edited by RaptorFighter
  • Thanks 1
Posted

Yep, I just mapped it.

 

    {pressed = iCommandSelecterUp, up = iCommandSelecterStop, name = _('Scan Zone Up'), category = _('Sensors')},
    {pressed = iCommandSelecterDown, up = iCommandSelecterStop, name = _('Scan Zone Down'), category = _('Sensors')},
    {pressed = iCommandSelecterLeft, up = iCommandSelecterStop, name = _('Scan Zone Left'), category = _('Sensors')},
    {pressed = iCommandSelecterRight, up = iCommandSelecterStop, name = _('Scan Zone Right'), category = _('Sensors')},

 

Scan Zone UP / DOWN is what you're after for antenna elevation.
 

  • Like 1
Posted

Never occured to me to press the middle MFD button !!!.

I'm going to take RaptorFighters approach and map the keybinds to my throttle hat switch to control the radar elevation.

In the "control setup"  menu i've already tried mapping my hat switch to the Scan Zone up/down commands.... but that didn't work.

When i get the chance i will try mapping my hat switch to the OSB 18, 19 & 20 MFD buttons. on the center display... hopefully that will work.

Thanks for the replies and enjoying the F-22 mod 🖕

Win 11 Home 64Bit, i7-13700K@5.2Ghz Water Cooled, 32 Gb RAM, PNY RTX4090, Pimax Crystal, Quest Pro, Realsimulator FSSB R3 ULTRA, Virpil/Thrustmaster Warthog HOTAS combo, MFG Crosswind Pedals.

Posted
10 minutes ago, Gunnergolly said:

Never occured to me to press the middle MFD button !!!.

I'm going to take RaptorFighters approach and map the keybinds to my throttle hat switch to control the radar elevation.

In the "control setup"  menu i've already tried mapping my hat switch to the Scan Zone up/down commands.... but that didn't work.

When i get the chance i will try mapping my hat switch to the OSB 18, 19 & 20 MFD buttons. on the center display... hopefully that will work.

Thanks for the replies and enjoying the F-22 mod 🖕

I was just able to map the Scan Zone ones and they worked correctly.  The issue with mapping the OSB buttons to the hat switch is you'd have to have a press/release type of command.  That is, note what the commands do above.  When pressed it moves, it when released it stops.

So, you'd have to map OSB 20 and OSB 19 for move/stop and the same for OSB 18.

The way the OSB's are set up, is that they continue to move to the end of the range unless you press stop.

 

Posted

Do i need to add the above .lua code in to a file somewhere or has it already been  included ?.

I will fire up DCS soon and try mapping them again....

Win 11 Home 64Bit, i7-13700K@5.2Ghz Water Cooled, 32 Gb RAM, PNY RTX4090, Pimax Crystal, Quest Pro, Realsimulator FSSB R3 ULTRA, Virpil/Thrustmaster Warthog HOTAS combo, MFG Crosswind Pedals.

Posted (edited)
24 minutes ago, Gunnergolly said:

Do i need to add the above .lua code in to a file somewhere or has it already been  included ?.

I will fire up DCS soon and try mapping them again....

It's already there.  I just copied it out of the joystick input file.  However, I'm experimenting with an idea on the OSB buttons.  I can have a single button press issue multiple commands.  So, I can send a series of "move" commands followed by a "stop" command on a single push of the button.

*EDIT*  Ok, that doesn't work for some strange reason.  And as I was doing it, I realized I'd tried that before.  That's why I added the stop button.  I couldn't get it to work any other eay.

Edited by Nightstorm
Posted (edited)

Just mapped one of my throttle hat switches to the Scan Zone up/down keybinds and its working perfectly in game..... i'm sure i tried that last night and it didn't work ????.

Nevermind it's working now :).. 

Thanks... 

Edited by Gunnergolly
  • Like 1

Win 11 Home 64Bit, i7-13700K@5.2Ghz Water Cooled, 32 Gb RAM, PNY RTX4090, Pimax Crystal, Quest Pro, Realsimulator FSSB R3 ULTRA, Virpil/Thrustmaster Warthog HOTAS combo, MFG Crosswind Pedals.

Posted

Poor little F-15's  😗

Win 11 Home 64Bit, i7-13700K@5.2Ghz Water Cooled, 32 Gb RAM, PNY RTX4090, Pimax Crystal, Quest Pro, Realsimulator FSSB R3 ULTRA, Virpil/Thrustmaster Warthog HOTAS combo, MFG Crosswind Pedals.

Posted (edited)

Doing some experiments in TacView with the custom version of the F22.lua.  I hit a max of 23 degrees/second with an instantaneous of 30 degrees per second.  Max AoA 30 degrees.

Not quite what the real thing can do, but considering we don't have actual thrust vectoring, it's not bad.

nullnull

image.png

null

image.png

Edited by Nightstorm
  • Like 1
  • Thanks 2
Posted (edited)

I've made some adjustments to the FM data for the custom set up to include elements from the PSA FM data.  Now, while the Raptor with thrust vectoring can do 28 degrees/second sustained at 20k feet, ours w/o actual thrust vectoring can't.  However, since the "simulated" thrust vectoring is achieved by increased pitch control, it makes sense that it would be most effective at lower speed and altitude.  And this was the result:  27 degrees/second sustained at 0.55 Mach with max instantaneous of 31 degrees/second.  At around 18k feet I did have a peak instantaneous of 43 degrees/second, but I think that's when it departed when AoA exceeded 30 degrees.

I'm not sure that it'll get much better than that.  I can include the modified custom file in an update here shortly.

While I was at it, I tested vertical performance, and it will in fact accelerate straight up.  And that's consistent with the published values of a thrust/weight of greater than 1:1.

  • Thrust/weight: 1.08 (1.25 with loaded weight and 50% internal fuel)

 

Single Player version updated.

 

null

image.png

Edited by Nightstorm
  • Like 2
  • Thanks 1
Posted

@Nightstorm Is there any way to easily remove the later Sidewinders from the mod? I'm asking as the Liberation Campaign is erroring out when selecting the F-22. I'll add a pic of the error shortly

Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO

64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS

Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP

Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir

Posted (edited)
9 minutes ago, MustangSally said:

@Nightstorm Is there any way to easily remove the later Sidewinders from the mod? I'm asking as the Liberation Campaign is erroring out when selecting the F-22. I'll add a pic of the error shortly

it’s not the sidewinder, all new weapon from this mod would lead you to error.

Don’t use the binary from Liberation, download the source from GitHub and build it yourself.  Generate the pydcs file of F22A again and do some little coding then you would be able to fly this mod in Liberation  

Easy to do with the instruction from Liberation GitHub wiki. 

Beware normally the raptor would dominate the sky in Liberation. I put the Felon mod in liberation as well but it simply cannot match the level of this mod.

Edited by FlyingAlex
Posted
4 minutes ago, FlyingAlex said:

it’s not the sidewinder, all new weapon from this mod would lead you to error.

Don’t use the binary from Liberation, download the source from GitHub and build it yourself.  Generate the pydcs file of F22A again and do some little coding then you would be able to fly this mod in Liberation  

Easy to do with the instruction from Liberation GitHub wiki. 

Beware normally the raptor would dominate the sky in Liberation. I put the Felon mod in liberation as well but it simply cannot match the level of this mod.

 

Sorry mate, have no idea what you are talking about!

 

Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO

64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS

Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP

Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir

Posted (edited)
3 minutes ago, MustangSally said:

Sorry mate, have no idea what you are talking about!

 

https://github.com/dcs-liberation/dcs_liberation/wiki/Modded-Aircraft-Support
 

read before play would be a good habit.

Remove sidewinder then you will see error of AIM120D. You need to tell Liberation about the new weapon in this mod before you can use it.

Or, you can use multiplayer version then all would be fine.

Edited by FlyingAlex
Posted

Mate pull your head in. Not all of us are programming geeks!

Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO

64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS

Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP

Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir

Posted (edited)
11 minutes ago, MustangSally said:

Mate pull your head in. Not all of us are programming geeks!

Then use the multiplayer version🙂 Simple!  
 

You can delete weapon.lua, remove the import from entry.lua , edit F22.lua for the pylon information as well. It should make you a single player version without new weapon. If I didn’t miss anything

 

*Edit 

or you can copy the FM table and thrust table in F22A.lua from single player and replace the stock one in multiplayer version F22A.lua 

Edited by FlyingAlex
  • Like 1
×
×
  • Create New...