Jump to content

Tj1376

Members
  • Posts

    554
  • Joined

  • Last visited

1 Follower

Personal Information

  • Flight Simulators
    DCS FSX MSFS
  • Location
    Middle of the United States!
  • Interests
    Flying, coding, fixing the broken

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ive found that the trim release button requires the rudder pedals (and joystick) to return to the neutral position or it gets 'stuck' and WILL NOT move. Ive started simply removing my feet off my rudder pedals after I press trim release (so they return to center) and then step hard back on them again. TJ
  2. But @104th_Maverick, inquiring minds really want to know how you got the George interface to the bottom right of your screen!!!! This video was great, but make a video on how to move George interface! TJ
  3. Having come from the KA50, the Huey and the Hip, the various Trim Reset buttons allowed the trim to recenter in the middle of the axis. This was INCREDIBLY helpful when you are transitioning from fast fwd flight to slow flight to enter the hover. As an example, enable "Show Controls" and follow along in your DCS AH-64D: Hold stick in a non-neutral position, press Force Trim UP (the manual calls this force trim release, because when depressed its letting go of the magnetic devices that physically hold the stick in place - your non FFB joystick cannot simulate this.) Return your stick to a neutral position. Now, verify in show controls that your stick is being held in a non-neutral position. Now, here is where the rub is.. and where many pilots (myself included) are struggling. In the KA50/Heuy/Hip, we now have a button to 'force our trim back to its neutral position' (what many are calling a 'force trim reset.') In the Hip, this button is "Trim- RESET to default," in the Heuy this button is "Trimmer reset," and in the KA50 this button is called "Trimmer reset." No such button exists in the DCS AH-64D. The only way I have found to get the trim back to its neutral position is to open show controls and physically move the stick back to neutral and then press Force Trim Fwd (release) to reset the trim near the neutral position. Could we please compromise on a factually unrealistic "Trim- Reset to default" button that we can bind, just like in the Hip/Huey/KA50, to help us overcome this hurdle? I realize the real chopper may not have such a feature (its not needed in real life), but for those of us who use centering springs on our joysticks, it makes life much easier. As always, appreciate your dedication. TJ
  4. I think the confusion that so many are having is that Force Trim Release doesnt do what folks expect it to do if they have transitioned from the KA50, Heuy or Hip. Having come from the KA50, the Huey and the Hip, the various Trim Reset buttons allowed the trim to recenter in the middle of the axis. This was INCREDIBLY helpful when you are transitioning from fast fwd flight to slow flight to enter the hover. As an example, enable "Show Controls" and follow along in your DCS AH-64D: Hold stick in a non-neutral position, press Force Trim UP (the manual calls this force trim release, because when depressed its letting go of the magnetic devices that physically hold the stick in place - your non FFB joystick cannot simulate this.) Return your stick to a neutral position. Now, verify in show controls that your stick is being held in a non-neutral position. Now, here is where the rub is.. and where many pilots (myself included) are struggling. In the KA50/Heuy/Hip, we now have a button to 'force our trim back to its neutral position' (what many are calling a 'force trim reset.') In the Hip, this button is "Trim- RESET to default," in the Heuy this button is "Trimmer reset," and in the KA50 this button is called "Trimmer reset." No such button exists in the DCS AH-64D. As some have suggested, simply hold Force Trim Fwd (release) and hold your joystick in its neutral position and release Force Trim Fwd. This does not work. DCS is not resetting the trim into the neutral position. The only way I have found to get the trim back to its neutral position is to open show controls and physically move the stick back to neutral and then press Force Trim Fwd (release) to reset the trim near the neutral position. This is not ideal in VR. So for now, I believe the answer is "you gotta trim trim trim." But I believe the ask from the community is a simple "Trim- Reset to default" button that we can bind, just like in the Hip/Huey/KA50, to help us overcome this hurdle. TJ
  5. Where are you finding the force trim release?
  6. Can confirm that I cant get althold to engage either, and the manual makes no mention of parameters to maintain to get it to engage. Im holding a pretty steady hover, wont engage. Im holding a pretty accurate attitude, trimmed out and not losing or gaining any altitude at speed and it will not engage. We must be missing something! As one of my friends said, ED needs to pay Chuck to build his guides into their manuals. Their manuals are great for 'how does a system work' but are not the best at explaining how you actually use said system. Althold is a prime example. TJ Page 63 of the quick start manual. Attitude hold is force trim left (althold is force trim right) TJ
  7. Can anyone clarify (or point me to the manual) on what the difference is between GND and GND DLY on the GBU31v3b? I have a test mission where we use GBU31v3bs to take out an ammo depot. Prior to the 12/22 patch, you had to put the GBU31v3bs into GND DLY to kill the ammo depot with 2 bombs on the F16. Post the 12/22 patch, you now have to put the GBU31v3bs into GND to kill the ammo depot with 2 bombs on the F16. Im sure this is all still WIP, so no bug report, but was curious what the 'correct' procedure will end up being. TJ GBU31fromF16withGroundDelayNotKillingBunkers.trk GBU31fromF16withGroundKillingBunkers.trk GBU31fromF18withGroundDelayKillingBunkers.trk
  8. No idea. All I can tell you is that tracks before this last patch had gbu31v3s in AIR mode defeating the bunkers. After this past patch, they no longer do (they must be in GND mode, although we supposedly do not have the correct fuze for this.) So probably still all WIP. TJ
  9. Did this get snuck into the last open beta release? Post this latest patch, I noticed my testing for the F16 started failing the ammo depot again (where 2 GBU31v3 would not kill the ammo depot.) Someone then pointed out that no, I was wrong that you had to use GND fuzing (despite our previous conversation where this was not actually implemented.) Sure enough, loaded the F16 test back up, this time set it to GND and boom, 2 GBU31v3s destroy the ammo depot. I then also tested the inverse, and sure enough, 2 GBU31v3 in AIR no longer destroy the target. TJ
  10. No. Satnav settings for blue are unrestricted. Basically someone once said "Russia will only be red" and a bunch of code was written around that. So once you put a non Russian airframe on red, you've gotta unrestrict satnav so the nato airframes on red can access the GPS data. You should have no issues following the same procedures on blue. But please confirm. TJ Sent from my SM-N970U using Tapatalk
  11. Date doesnt matter - coalition choice does. If you happen to be flying RED, and unrestricted satnav is FALSE, your bombs are dropping via INS. You can also update this by just opening the mission in the mission editor, going to the checkmark on the left hand side (called 'mission options') and selecting both checkboxes for unrestricted satnav (enforce and value.) Then, save the mission file. Next, go to YOUR settings, go to gameplay tab, make sure unrestricted satnav is checked. Try again. Also edit, your steps are spot on accurate. Without being able to see your track (because your mission file requires some sort of mod), just verify you are flying red. Try flying blue and see if you have more success. TJ
  12. In your mission, try turning ["unrestrictedSATNAV"] = false, to true and make sure in your game settings it is also set to true (by default its not selected.) It is located in Options > Gameplay page. In a single player mission, both the clients game settings AND the mission must have this value to true. I am unable to verify which color your AV8B is and I dont have the mods you have to verify or the time to decode the coalitions in your mission file.... But ["unrestrictedSATNAV"] = false, has caught many mission builders out and causes GPS bombs to drop with just an INS alignment which means they miss by just enough. TJ
  13. Latest open beta Persian Gulf map Single Player (although reproducible in multiplayer as well) Scenario is one "Warehouses > Ammunition depot" unit - mission has both the Viper and the Hornet with GBU 31v3 (penetrating warhead) Fly to objective, release one GBU, do a jink, release 2nd GBU. (The jink is to make sure when the first GBU explodes it doesnt take out the 2nd GBU from splash damage.) Watch both GBUs hit target Expected Result: 2 GBU31v3's hit target - target destroyed Actual Result: Hornet - success (2 31v3s destroys the ammo depot) Viper - failure. It is inconsistent how many GBUs it takes, sometimes 7, sometimes 10, sometimes 9) Please review and advise, thank you for your dedication. TJ f18TwoGBUwithPenetratingWarheads.trk TenGBUwithPenetratingWarheads.trk
  14. OK- im going to create a bug report. If you use the 31v3 on the hornet, it takes two to kill the depot. And while I thought you were wrong about the fuze settings, I even put the 31v3 on instant fuze in the hornet and still it only took two 31v3s to kill it. Really odd that the exact same weapon provides different damage values between the two platforms. TJ
×
×
  • Create New...