Jump to content

-Pv-

Members
  • Posts

    183
  • Joined

  • Last visited

Everything posted by -Pv-

  1. Repair fixed the problem. I now have full control over FLIGHT/ATC/AWACS/JTAC as I have in the past. I know I have not modified any files between when this all worked last and after a recent online update when this all broke. I'm pretty sure the update broke some unknown file. -Pv-
  2. Many factors contribute to making aircraft control in sims harder than real life and these have been mentioned above, so summary: 1) We cannot feel the Gs. 2) We only have flat world visual as cues with no or little peripheral. 3) Our controllers (no matter how well constructed or featured) are not exactly like the real world aircraft. 4) All the software we use (profiles, sensitivities, etc.) further the complexity of matching hand/eye coordination without other sensory information to precise motion control (or the illusion of it.) 5) Combining twist rudder with stick is not a real world aircraft feature which removes an intuition factor from the sim and adds a control interaction complication. This is a sim. It's not perfect, and for the price and the hardware/software we use to run it, can never be exactly real world. So, we learn tricks and spend more time practicing than real world pilots do to train our brains to the limitations. -Pv-
  3. This seems to be a new problem I haven't had in the years I've been playing this sim. Angles close to the Sun saturates the HUD. -Pv-
  4. I ran the repair and the result is the before and after files are identical (I ran them through a file compare program.) Tech support claims my mic switch assignments are "customized" so do not work. Here are the entries which tech support claims is incorrect: {combos = {{key = 'Num+', reformers = {'LShift'}}}, down = iCommandPlane_HOTAS_MIC_SwitchUp, up = iCommandPlane_HOTAS_MIC_SwitchOff, name = _('HOTAS MIC Switch Up'), category = _('HOTAS')}, {combos = {{key = 'Num-', reformers = {'LAlt'}}}, down = iCommandPlane_HOTAS_MIC_SwitchDown, up = iCommandPlane_HOTAS_MIC_SwitchOff, name = _('HOTAS MIC Switch Down'), category = _('HOTAS')}, {combos = {{key = 'Num-', reformers = {'LShift'}}}, down = iCommandPlane_HOTAS_MIC_SwitchLeft, up = iCommandPlane_HOTAS_MIC_SwitchOff, name = _('HOTAS MIC Switch Aft'), category = _('HOTAS')}, {combos = {{key = 'Num+', reformers = {'LAlt'}}}, down = iCommandPlane_HOTAS_MIC_SwitchRight, up = iCommandPlane_HOTAS_MIC_SwitchOff, name = _('HOTAS MIC Switch Forward'), category = _('HOTAS')}, Here is a screenshot which should be easier to read: https://www.hightail.com/download/bXBhQmtYQzN3TGdzeHNUQw I've been struggling for about eight days now trying to fix the problem with not being able to control AI in the game. After an exchange of many emails the tech says my mic assignments are over-riding the default. I have done the following: Deleted the directory: \Saved Games\DCS\Config\Input\A-10C Ran DCS World Repair. The mic assignments in the UI Controller screen and the default.lua file itself have not changed. -Pv-
  5. "Does anybody know something about roll stability mechanisms in modern fighter jets?" The F-16 in particular is one of the most agile fly by wire fighters ever developed. You cannot expect the A10 to fly like an F-16. Due to its lower speed though, it's good enough. More than anything else, I think it's training your brain and muscles to react to what you see while learning the feel of your controller. The more you customize the controller, the better. -Pv-
  6. Anyone wanting to save this PDF file to their drive, use your browser's File Menu and click Save File As... I use Firefox to do this. IE should be the same. A big improvement would be to make the index clickable. -Pv-
  7. I have Warthog unlocked. FSX throttles locked together. -Pv-
  8. According to Eaglesoft tech support my default.lua file is corrupt. How can I get a clean/current one? -Pv-
  9. I haven't experienced this. I see no reason for the programmers to code in a feature like this *on purpose* without telling anyone they have a time limit to request ATC services. Seems implausible. To test this, do an auto-startup, then wait for as long as it usually takes you to request taxi and take off to see if the AI goes to sleep. This is assuming request startup is not your only problem which you should be able to do immediately on starting the battery and tuning radio. -Pv-
  10. I've been using my own custom built for X-65X for years. I suspect it's not as full-featured profile as offered here, so haven't uploaded it. I haven't programmed shifted features using pinky or Button C combos because of the shape and size of the stick makes it too hard to activate two switches at once while keeping control of the axis with the same hand unless you have very large hands. Mine are at least average or larger because I can play 10th chords on the piano. This controller is certainly one of the more rugged out there and no pots on the stick axis adds years to it. No tactile feedback from stick movement does cause me to over-compensate by yanking harder on it than I need to which causes some muscle strain. -Pv-
  11. One thing strange for sure is the AI ability to land stop in 50 feet no matter the payload. Also, my wingman can pass me up half way down the runway with the same payload despite starting the roll a little later, so there is some evidence the AI does not have the same dynamics as the human player. -Pv-
  12. How are we expected to operate the TF-51 if there is no manual, training or key chart for it in DCS World? I realize it's a demo. -Pv-
  13. " 'Takeoff' used to be used in departure clearances until a 747 pilot heard it, tried to takeoff then plowed into another 747." Actually, the pilot in question got impatient. The controller withheld take off clearance because he could not see the 747 that just landed. The departing 747 took off anyway causing one of the biggest airline disasters in history. Has nothing to do with how to properly configure the altimeter in A-10C so I just supported a thread hijacking and derailing. -Pv-
  14. It's been a long standing consensus the quick missions have too much and too aggressive enemy aircraft. You can turn them off and concentrate of anti air avoidance. Still the missions place all forces within reach of each other right at the beginning as if there was no warfare at all until everyone could see the whites of their eyes. Not realistic in the modern battlefield. These missions are not recommended for learning. If you search the file library here, you will find "training" missions at various difficulty levels. These generally work better although some of them are still too hard for the beginner. -Pv-
  15. Keyboard or stick trim shouldn't matter. All the stick hatswitch does is send one tap at a time to the keyboard command. Holding the hatswitch is like holding the key down. Flying formation is a complex balance of altitude, power, 3 axis stick control and trim. All three of these controls in the sim (throttle, aileron, elevator) are rather course (no matter how carefully I null and contour the stick. If nothing else but the trim is adjusted for finer control, air tanking would not be quite the frustration it is. The problem primarily is how the trim is coded to provide too much pitch moment per increment. If trim had a better control profile, obtaining a trim/power ratio would be easier. -Pv-
  16. I discovered the hard way that some missions force default views. If I try to save custom snap views within these missions, the snapviews get saved as default again when I exit the mission even though my custom views worked for that single flight. I've decided that if I fly a mission and the snapviews are default, to exit the mission and toss it rather than spend hours fixing stuff over and again. Mission designers, please take a note that as new WH versions come out, these defaults change over the years so when you force people to use views they are not used to, it's not a welcome feature of your mission. Please do not do this. -Pv-
  17. Another problem related to these snapviews. They don't appear to save after exiting the mission. I tried looking in the keys for a command to save the cockpit like Falcon4 has, but I couldn't find anything. The "Save Profile As" lights up but doesn't appear to function in the sim. Would be a huge downer if I have to set these up new for every flight. Added: I see the option in the UI is enabled to save user snapviews. I still lose them every time I end a flight. -Pv-
  18. nice one r813. Stay focused on the guy asking for help and off the soapbox. Many people when asking for help are at first angry and the only way they know how to start is by expressing their anger by asking with a challenge. After a while they cool down and that's when you can inject specific answers. -Pv-
  19. For some reason numpad-3 won't save but the others are working GREAT! -Pv-
  20. I don't have TIR but what you described works great thanks. What was not intuitive to me is the interface remembers the snap keys I pressed last and saves it with the num0 key After I've moved the view around. Not intuitive. Nice. -Pv-
  21. "Yes I do. I just checked. Also get HUD with NumPad-5. 4 and 6 are MFD." In mine, 5 is Hud, 1,3 are MFDs and the others all look outside. Wish these had not hanged. They used to be: 1 = left radios 3 = right radios 5 = HUD 7 = Left MFD 9 = Right MFDs I don't remember what the 4,6 were because I didn't use them enough. Any idea how to create view(s) that do what I want (snap to a closeup of the left and right consoles?) -Pv-
  22. I did as you suggested and the lua files were replaced with new ones dated today. Nothing changed. The Win snapviews are the same (mostly useless) views they were before the repair. Starting to wish I had backups of the snapviews file before the upgrade. Who would know they would change? "My View folder is dated 13 Jan 2014." Looks like they get time stamped to the day you do the repair. -Pv-
  23. Mine is dated 7/22/2013. Are you implying when you use the snapviews you get the same ones as there have been there from the beginning (the two radios on the left and the CDU and ILS radios on the right?) All I get are the two MFDs and all the others are look outside views. -Pv-
  24. Yup. I've read this advise and the one that always comes after it "practice practice practice" and there comes a point where it's all for nothing because for whatever reason I cannot do it. The fine control is just not there. Fortunately there is plenty to do in the sim without it. Also, the Balkans world is just not big enough to need it on a practical mission. Wishing didn't have to disable the gun mode for tanking. That would be perfect. -Pv-
  25. The keycommand shows my LWin-num0-9 are still configured to snap0-9 but I don't see any way to define what those snaps look at. Only two of them are useful to me so if I can change them back to what they were before the upgrade that would be most helpful. -Pv-
×
×
  • Create New...