Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Thanks, @tea_cypher. I just got back from travel last night and spoke to a friend who has the hornet stick. He said pretty much the same thing. I was worried about the &JoystickF18 address in TARGET and was afraid I would need new nomenclature for everything, but it sounds like DCS and TARGET still sees it as a Warthog stick. This makes it very doable. Have you tested whether you can change between the Warthog and Hornet stick while the profile is active, and without the profile dumping. I imagine this would work, but I want to make sure before starting to code. I can do the Hornet and Harrier based on these button assignments, but no plans yet for anything else.
  2. You mean they don’t use brown sky for flights out of KLAX? [emoji38]
  3. F14 RIO use of Ground Stab Ok, my misunderstanding in nomenclature then. I was referring to HCU to Radar and half-trigger to bug the contact on the DDD. Edit: unless of course we are talking about the same thing, just differently. I thought that HCU to DDD was only used for a radar fix.
  4. At the end of the video, you indicate that you should use Super Search (DDD) instead of pushing the button. I assume you're referring to bugging the contact on the TID and then pressing PD-STT. While I know the WCS conversion to STT (i.e. push button) isn't as reliable as Super Search, I would think that in this case the WCS conversion would automatically resolve the range ambiguity you encountered. Just wondering if there's any reason (technical or bug related) that makes you prefer Super Search.
  5. The only thing I can think of is that you may be pushing the mic switch left or right instead of down, especially since direction is relative to the throttle arm instead of the desktop. I tested last night and couldn't duplicate the "Stick buttons... Done!" message without going left or right on the mic switch, which is by design. Code checks out too.
  6. It is now. Make sure you set Cougar MFDs to 0 in CTS, then you can use S3+SPDB/T9 Long to enter profile selection mode and Hat2 to cycle selections. Details are near the end of the User Reference.
  7. Looking at the code, MSD shouldn't remap anything at all. As long as you have it set to Jester (which should be default, though you can switch it for multiplayer/AIRIO with S3+LOSB16), all it does is hold shift, press A, and release shift once you release the button. The "Stick Buttons..." message should only occur when you remap the stick, which IIRC happens in 3 cases: You change seats (e.g. Pilot to RIO) You raise or lower the gear. You exit CommState (which is entered when you hold MSL/R), at which point the stick is remapped to its previous configuration. Just to confirm, you are using the HOTAS Warthog (i.e. not a Cougar), right?
  8. Another data point: the TALD reduces performance and ceiling (likely parasitic drag), even after launching all TALDs. However, jettisoning the racks puts the jet's perfomance back in norms.
  9. Be sure you create the modifiers for every module So Far So Good, except you don't need to load the diff.lua for the keyboard (it says js in the filename). This could be the problem. The UI Layer diff.lua is only for the Interface. For the module, stick with the TARGET Mi8 xx v230.diff.lua files for keyboard and joystick You need to read Appendix D in the Setup Guide PDF. I recommend reading the setup guide all the way through, as it will hopefully give you some context. This isn't a script you want to jump into without reading the manual.
  10. First, if you are using a VR solution, you should set Head Tracking Hardware = 2. You also need to follow the directions for VR in the Setup Guide PDF, and apply the diff.luas both to the GUI tab and the applicable modules. I'm inferring that you added the diff.luas to the module in question. Next, check out the section in the User Reference (HTML) titled "Deviations for Virtual Reality Configurations." Depending on which module you're using, you will likely need to double-tap the hat switch to switch positions. If you still have issues, we can further investigate. That keypress duration seems awfully short, though.
  11. The way inertials work (assuming ground start; SINS alignment is a different animal) is that you input your present position. Then when they first spin up, they can detect the direction of the earth's rotation. From this direction, they take a 90 degree offset to calculate True North. In fact, some inertials can detect the amount of rotation and determine your latitude, and will tell you if you have input your latitude incorrectly! True North is the basis for INS navigation, and no magnetic source will change this. The only reason magnetic headings are calculated by the INS is for the pilot when dealing with systems, sources and procedures that use magnetic headings (e.g. navaids, ATC, approaches/departures). For over water navigation, we always used true heading and switched back to magnetic when in coastal range. Regarding your second paragraph, since the AHRS is the magnetic source for the Tomcat INS, any inaccuracies (magnetic deviation) will affect the INS calculated magnetic heading. However, the true heading remains consistent.
  12. When they spin up, the first thing inertials do is determine true north. An INS knows true headings, and magnetic headings are abstracted. I'm not a tomcat guy, so I don't know exactly how the Tomcat INS works, but the LTN-72 I used had magvar in its database and applied it based on present position. You can also manually apply magvar in the CAP based on the number present on the kneeboard. Bottom line: magnetic deviation does not affect the inertial's recognition of true north, nor degrade its accuracy.
  13. I have experienced this both as Pilot and RIO (I was the Tomcat pilot in the video). This was a sandbox mission with minimal scripting in order to keep everything as simple as possible, and both pilot and RIO were physically in the state of Virginia (i.e. minimal chance of geographical lag). We have consistently experienced these issues, along with massive desynchronization, with multiple pilot/RIO combinations on multiple servers and missions across multiple versions of DCS. Here are links to my TacView and Track of the flight. Note that things look a bit different from my perspective.
  14. 2.34 Hotfix 2 is out. Changelog: Remapped Mi-8/UH-1 LOSB01 NS430 mapping for consistency with other modules F-86: Fixed S2 mapping for Warthog. AV-8B: Fixed keyboard fuel probe mapping
  15. So what you're saying is that it's pressing as it should, and it's mapped in DCS Options, but it's not recognized in DCS Options. If it isn't recognized in the Options menu, I'll look into it. If it is recognized in the DCS Options menu, there's not much I can do about it in-game.
  16. The latest beta (33184) fixes this. Do you still have the issue, even after reloading the diff.lua files?
  17. Welcome to DCS! You are getting into a very rewarding sim/hobby, but one with a very steep learning curve. As much as I love that you are using my profile, you may wish to skip TARGET for now and use the default Warthog mappings for the Ka-50. This serves to eliminate variables, so you know if something doesn't work that it is not whether you set up the TARGET profile correctly. Once you are comfortable with DCS, its controller interface, VR, and the Ka-50 itself, then you may wish to revisit TARGET. Much of my instructions rely on existing knowledge of the DCS controls and options menu, and using my profile will prove to be much less frustrating once you develop a foundation of knowledge in DCS. Understand that I'm not trying to insult you or push you away. I just think that learning DCS without having to follow the exacting steps in also learning my profile will benefit you a lot more in the short term. I look forward to your return once you understand the basics.
  18. I'll fix this in next version/hotfix. In the meantime, the solution is to find Air refueling probe toggle IN/OUT and add the following to keyboard: LWIN+A
  19. 1) Since the TID is analog, give quick relative approximations. For example, if you're in 20 degree azimuth (that's 20 per side) and your contact is halfway to the left bar, call for 10 degrees left. Same with range: approximate until you can refine. In cases like this, timeliness is more important than accuracy. 2) A technique I use is to match my DDD range with the TID, so when I don't have a target bugged the IFF compares directly to the TID. +10EXP is when you have a target bugged (either in TWS or STT), and it centers the bugged target in the DDD and gives you a view of the surrounding airspace. +10 refers to the 10 nautical miles surrounding the bugged target. 3) EDIT: Sorry, I just re-read your question. You are correct in that the ground-stab vectors are absolute/true heading and aircraft-stab vectors are relative. 4) For bar scans, the answer is "it depends." If I have a datalink picture, I can reduce my azimuth and bars to a combination that gives me a shorter time between contact pings, but if you're pretty much the biggest radar out there you may need the wide azimuth 8 bar scan. Also, based on your altitude you should point your radar elevation to maximize the bars you have to the likely altitude bands of your threats.
  20. 2.34 Hotfix 1 is up. Fixed F-14 Pilot Warthog diff.lua file. Fixed minor bugs with Warthog CommState and APU switch assignements. Fixed VR Mouse Scroll Wheel for Cougar users Fixed HOTAS module cycle not working for MiG-15 and modules without speedbrakes.
  21. Yeah, don't trust the exemplars near the first post. I don't bother to update those.
  22. Thanks. Didn't even think about the planes without airbrakes. I'll figure something out.
×
×
  • Create New...