Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. Is that also the code to play Asteroids on the Supercarrier deck? :smartass:
  2. I wasn't able to duplicate the error on either the Su-25 or A-10A. The only thing I can think of is that a Tusba TQS does not connect to the profile (it's seen as a separate controller), so you should not set Warthog Throttle to 2 in the CTS settings. Other than that, please post your dcs_world.tmc file so I can try to duplicate the error with your settings.
  3. Sorry, fellas, but real life conspired against me and I won't be able to produce a hotfix, and the 2.44 release is on hold until February. In the meantime, just go to the DCS Options menu and Map Coolie Hat Up to ANT ELEV Knob - CW and Coolie Hat Down to ANT ELEV Knob - CCW. You can find these in the F-16 controller by pressing = and - respectively.
  4. Upon further review, it is already possible. In the CTS Values tab under DCS: M-2000C, set "Airbrake Type" to 0. I'll update the database to make 0 the new default value.
  5. DCS World TARGET profile for TM Cougar and Warthog + MFDs I can certainly make that happen. This describes the “binary-momentary” brake type in the CTS user reference, so this should be a simple fix.
  6. I think the antenna elevation command remapped in the module. I'll have this updated in 2.44, or in a hotfix if 2.44 isn't available shortly.
  7. There’s only so much room on the graphics, so they default to TrackIR users. I recommend giving the user reference a read, and definitely look at the hat1 section as well as the section for any module you fly (e.g. M2000C).
  8. I don't recommend modifying the script, especially for the F-14 which reassigns a lot of assignments on the fly across a number of functions. For 2.44, I have inserted Spyglass Zoom wherever possible to a "down" SnapView, and VR Zoom to an "up" SnapView (in addition to the existing H1U toggle and TriggerZoom). Being able to assign UI Layer commands to the keyboard has really opened up this functionality (previously, all UI Layer commands had to be DirectX). Thanks for the heads-up. The C-101 devs changed a lot of mappings and I didn't catch them. No promises for 2.44, but I'll get on it as soon as I can. Master Arm and Gun Arm are mapped to the EAC and RDR ALTM switches on the throttle base. Additionally, MFDs are highly recommended for use with CTS, as this was originally designed to integrate the MFDs so that functions don't need to be shoehorned to the HOTAS. I have made the profile less dependent on MFDs to support VR users, but that does not change the intent of the profile. I highly recommend purchasing headtracking (or VR), rudders, then MFDs (if VR was not purchased).
  9. Yes. I'm assuming that Push On/Release Off is the intended function (because it makes the most sense), but the function is currently a toggle and I wanted to ask.
  10. There’s no spyglass zoom in the profile...yet [emoji6]. Wait until next version.
  11. Similarly, enemy beacons that are on cannot be trusted due to "Meaconing," which means that the enemy can tune a VORTAC to the desired channel but put it on a truck and move it elsewhere to confuse or deceive aircrews. Anyway, the answer to the OP's question is "it depends." The OP already mentioned that a visual fix is best accomplished at low level. A low level drop is where INS accuracy will be most necessary, so this would be something along the flight route, and this is actually where the idea of the IP originated (a known visually identifiable position to update navigation prior to run-in). For high altitude, if your INS is that bad then maybe a high altitude fix, while less accurate, would be an improvement. Also a datalink fix with your wingman would get you within a few hundred feet +/- the wingman's INS drift. When I flew, the INS usually wouldn't drift more than 1-2 miles over the entire flight. That's generally enough accuracy to get you to where you need to be to do what you need to do.
  12. In other news, a hotfix is up that fixes the POV station switching as well as re-enables the AV8B SSw Push for the Warthog with the F-18 stick. Just run the CTS updater.
  13. Sorry, Rum_Runner. I read your post earlier, but I've been so busy I haven't had an opportunity until now to respond. What you described in The device analyzer (S4 presses DX29,31,32) indicates that the logical gear state is down (the DX29 combos are used for wheelbrakes with S4 when the gearstate is down). If the logical gearstate is up, S4 should press DX4. You must have the logical gearstate up to cycle and engage TriggerZoom, and you will only see DirectX commands in the device analyzer if you are using VR (you will see DX1 and DX29). You will see the keypad * and / or ENT in the event tester if you are using TriggerZoom with TrackIR or POV. If you have any further questions, please also list the module/profile you are using (not all profiles support TriggerZoom), your hardware (Cougar/Warthog/TrackIR/VR), and the steps used to replicate the error.
  14. Ok, I figured it out. When I put in a check to prevent remapping when the station wasn't changed, I didn't do it right for POV. Open DCS_World.tmc in the TARGET Script Editor, compile it, then find the file called DCS_Global_Subs.tmc in the left column. Then navigate to line 3297 which should read else if (TrackIR > 1) Replace this with else if (TrackIR != 1) This will be fixed in he next release. I'm too far along to do a hotfix right now, so for now you'll need to do this yourself.
  15. Read the HTML User Reference for any questions you might have. You should be able to go directly to the section you need. Not trying to say RTFM, but there's a lot of stuff there that is hyperlinked and may help to explain the profile. For example, with TriggerZoom (the S3+TG1), you actually need to press S3+TG1 to toggle the function (so you can turn it off whenever you like), then if TriggerZoom is active, holding TG1 will zoom in and releasing TG1 will zoom out. TriggerZoom can only be enabled if the logical gearstate is up, and is forced off when the gearstate is down. Great stuff! The HOTAS graphics are split right down the middle between throttle and stick, so you should be able to just bisect the image vertically to create your images. The only thing you'll chop is the special instructions. Also, you can use Kneeboard Builder to figure out the structure. I'm looking into this right now.
  16. I would consider the A2A school equally important as A2G. IRL, RIOs know as much about BFM/ACM as the pilots (providing insight and observations), and senior RIOs provide advice and direction for junior pilots in ACM. Also, since RIOs normally handle 99% of the comms, understanding the geometry and having SA is vitally important for communicating with the rest of the section/flight. As far as a formal curriculum goes, I'll have to kick the can until late spring. Real life has me bottled up until then.
  17. That's just a level of verification so the channel isn't spammed by randos and bots.
  18. The SnapViews are optimized for 1920x1080, so if you have an aspect ratio other than 16:9 they may be off. Unfortunately, the link to the ED Wiki in the HTML docs is 404, so I'll need to add instructions on how to manually modify SnapViews into the docs myself. For POV, try double-tapping the hat switch left or right without holding S3. The instructions on the graphic are for TrackIR users. Left should do RIO and right should do Pilot.
  19. I can take this one: IRL (or at least when I went through the NFO pipeline) we had 25 hours of stick time before being put in the back seat to do navigation and other NFO things. Going through the DCS Academy pipeline will help build the airmanship skills that will transfer to being a good RIO. From there, systems management for a RIO is not much different from being a pilot in a full fidelity DCS module. However, acting as a RIO (or any NFO role) is learning a mentality and being proactive. If I’m your instructor this summer, I’ll go into that. Right now, do the basic syllabus, then do the RIO training missions that come with the F-14 module. Everything you learn will be of use later.
  20. I caught this the other day. Run the updater, then import the latest keyboard diff.lua for the F-16 and the problem will fix itself.
  21. He's also referring to the PTID, which is a huge LCD screen instead of the "fishbowl" CRT we have in the current model.
  22. You definitely need to be running the latest version of TARGET.
  23. What combinations specifically are you trying, and what do you see on the Device Analyzer or Event Tester?
  24. Chuck, I'd say you outdid yourself, but your stuff is so consistently top notch that all you can hope to do is tie your best!
  25. This is actually due to the Pendular pedals. https://forums.eagle.ru/showthread.php?p=4134296&highlight=TFRPHARudder#post4134296 The post shows the workaround (remming out the TFRPAHRudder line) So my question: are you running TARGET v3.0.18.328 v2? Since you're the second person to recently bring up this issue, I'm wondering if Thrustmaster renamed or removed the TFRPHARudder alias for the pendular rudders. I'll also download v2 and look into this.
×
×
  • Create New...