Jump to content

GPatricks

Members
  • Posts

    651
  • Joined

  • Last visited

Everything posted by GPatricks

  1. I edited this out of the manual, will make my own "Scramble essentials" and Normal Startup list once we know what we have.. F16 Startup Procedure.pdf
  2. Complete module, as in actually finished before the next one? Let's not start talking crazy here...:lol:
  3. I succumbed to peer pressure, just pre-ordered... :lol:
  4. 2 years later, Win10 ver. 1903 Build 18362.535 (12/20-19) and my Lilliput Touchscreen works perfectly, just be sure to download the latest eGalaxTouch (5.14.0.18411) and Displaylink (9.3 as of 12-18-19) drivers and toss the CD that comes with it!
  5. This mod changes (most of) the gauges to English and offers three levels of glare reduction. It starts at 50% I believe which to me solves the issue, but you can go higher.. https://www.digitalcombatsimulator.com/en/files/722567/
  6. I just can't believe he didn't open up with his guns, I couldn't have resisted! :D When is this being implemented, two weeks?
  7. That's great news Capt Zen, I am going to be using two 8" Lilliput Touchscreens, assume I can make that work for MFD extract? Look forward to a new version of Helios!
  8. I find the F86 the easiest to fly and to me is the next logical step after prop planes, but I don't own the F18 or F5. The Mig15 is a bit more demanding to learn...
  9. Mig15 and F86 BEG for a Korean theater!! Anywhere else makes no sense for them..
  10. They were always crap.. only Iran claims Iraqi kills using it, and thats' likely BS too! You are correct, they are supposed to hit Mach 5 and climb to between 80 and 100,000 feet, then dive on target. "U.S. combat experience - On January 5, 1999, a pair of US F-14s fired two Phoenixes at Iraqi MiG-25s southeast of Baghdad. Both AIM-54s' rocket motors failed and neither missile hit its target. On September 9, 1999, another US F-14 launched an AIM-54 at an Iraqi MiG-23 that was heading south into the no-fly zone from Al Taqaddum air base west of Baghdad. The missile missed, eventually going into the ground after the Iraqi fighter reversed course and fled north."
  11. Have a regular RTX 2080, have Vsync on in game using 165Hz capable Gsync monitor at 144Hz, no issues.
  12. I play only single player at this time, but I will say that my favorite times playing were using the multiplayer dynamic campaign with 1-3 friends in that "other" sim. Start a campaign, fly a few sorties with friends, save it, start it where you left off, rinse and repeat. A server running a campaign in real time is fun also if it's private (VFW), just can get out of control if open to anyone with people hopping on and losing plane after plane because they don't give a crap..
  13. Weirdest thing, I installed the DCS Beta today and the cockpit panned right out of the chute for every plane, looked and the POV keys were assigned to the View Slow functions. Set up my other keys the way I like, saved the P51.diff.lua file, copied it over to the 2.5.5 standard version and loaded the config. Same thing, view does not move with the POV hat! It's like something is locking it in place, most likely some key I have ticked wrong.. darned if I can find it! Went to the extent of taking pics of the Beta Setup tabs, copied them exactly in the non-beta, same results... and it's ALL planes. Just copied the entire Config folder from beta to 2.5.5, STILL no panning view. WTH??? Uninstalled DCS, downloading fresh copy, see what happens! New copy, works perfectly.. Drastic move, but all good now!
  14. WOW, I need 91GB free to install the open beta??
  15. All POV hat settings on the slow settings (see pic), but now nothing happens when I use the hat... The CTRL+NumPadx work, the Win+Numpadx works.. I went back and set the POV U/UL/L/R/D to Camera View Slow and DL and DR to Snap view 4&6 for rear corner views and now its ok until I break the TIR5 out. I was hoping to be able to "free pan" using the hat but guess that isn't possible?
  16. I swear I tried the View slow and got nothing but I will try again. I have a new TIR 5 in a suitcase, so it stays until i'm settled in my new place i'll try it but I found TIR 4 to be a PITA... maybe i'm just too old school.
  17. Is there a way to set it up to "Freelook" around the cockpit using the POV Hat? I am using a combination of the camera views and the Win+Numpad 4&6 Snap view for rear view, which really are not all that good (too low). I would like to be able to pan around using the hat and snap back to "neutral" using a DX button or the F1 key, is this possible?
  18. Welcome back! Any chance you will produce the CH Fighterstick kits again? :thumbup:
  19. Ahh, for the P51 all I thought all I had was something about degrees of hand movement, nothing else.. until I clicked on P51 once IN the Special tab. There are a few choices there, one is auto-rudder which was unchecked (though maybe it should be ticked as my rudder pedals are still in a suitcase and I use the Z&X pedals to move it, not a good solution)..
  20. Back on subject, the Autotrim option is in 2.5.5 (not beta) and it can cause some odd behavior if ticked, I just posted this with a video link showing it yesterday in the P51 forum - "I have deadzone set to zero and in the calibration screen it shows even the slightest deviation from the center axis in both X and Y and re-centers perfectly every time. The issue is in the sim when flying, I move the stick slightly and nothing happens for the first few degrees, then it (the game stick) jumps to the current joystick position all at once. Watching the stick in the plane shows this clearly, no movement for first few degrees of motion then bam, stick pops. It's like its storing the start of movement and then sending it all at once after 1 sec or so. After this first few degrees of movement all is well and inputs on the stick parallel my movements exactly. This occurs in both the X and Y axis." This was solved by un-ticking Autotrim... the 10 sec. video is here, keep in mind I am slowly moving the stick for 2-3 seconds before the stick jumps each time.. https://forums.eagle.ru/showpost.php?p=4026201&postcount=3
  21. BINGO, you win Tintifaxl! I had Autotrim enabled (also saw the VR Headset was enabled for some reason). Unticked both, now the input is smooth as silk! Didn't see an auto-rudder option? Thank you!
  22. Checked, nothing assigned but CH Control Manager, pic attached.
  23. Thanks Aurelius, Game Controller Settings points me to use the CH Control Manger and everything is perfect there. Dead solid, no jitters, perfect calibration just like it shows in DCS Axis Tune for X and Y. The slightest pressure on the stick produces the beginning of movement, can't imagine it being any better! I'm going to try it with CH Control manger closed out, see if that makes any difference. For DCS I don't really use it, I have a Profile called "Nothing.map" that resets all the buttons to DX mode and I just assign buttons per the "P51 Real" keychart in game. Same results with Control manager closed. Here is a link to a short video of what is happening, keep in mind I am moving the stick very slowly for 2-3 seconds before it "pops" each time.. https://drive.google.com/file/d/1ILmXHSeoVxpfH5R3ptxSEi8ZVk5Uhy27/view?usp=sharing
  24. SOLVED- AutoTrim was ticked, un-ticked and all is well! It may be in other modules but right now i'm learning the P51D so lets start there. I have deadzone set to zero and in the calibration screen it shows even the slightest deviation from the center axis in both X and Y and re-centers perfectly every time. The issue is in the sim when flying, I move the stick slightly and nothing happens for the first few degrees, then it (the game stick) jumps to the current joystick position all at once. Watching the stick in the plane shows this clearly, no movement for first few degrees of motion then bam, stick pops. It's like its storing the start of movement and then sending it all at once after 1 sec or so. After this first few degrees of movement all is well and inputs on the stick parallel my movements exactly. This occurs in both the X and Y axis. Do I need to set up a curve of some sort? Add a deadzone? I posted this in the Input section also, maybe its just this module? Thanks for any help, makes precision shooting/flying impossible.
×
×
  • Create New...