Jump to content

Home Fries

Members
  • Posts

    3368
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. The T-45 is based on the DirectX module, and it has been a while since I addressed it. I will take a look to see if I can duplicate your error. In the meantime, please send me your dcs_world.tmc file so I can analyze your configuration. This will likely help me to duplicate the bug. In other news, the Apache profile just went into beta testing. I think it's a good start. After this, my focus will be on CTS 3.0, as I'm running out of stack space to add more modules the way TARGET is set up. The 3.0 will focus more on DirectX, which means fewer macros and more commonality across profiles (at least as far as TARGET is concerned).
  2. Version 2.63d (Hotfix 4) is released. It updates the I-16 to the DCS 2.7.15 standard and tweaks the RPM/Mixture routine. The I-16 custom lua is now obsolete.
  3. I am working on it, but I've had RL things over the past month. No ETA, but I am hoping to go into beta within a couple weeks.
  4. Usually as RIO, if I don't have a contact within 10-15 miles, I'll call for the pilot to use PAL or I'll give him one of the VSL modes. It's also a good reminder to get the head out of the cockpit.
  5. If you do take over the radar, make sure you let your RIO know ahead of time. Otherwise, your RIO will likely make disparaging remarks about your lineage when he has to rebuild the picture he's been working on.
  6. Are you using VR? If this is the case, then that mapping is correct. You can also set that mapping manually by setting Warthog: Boat Switch as Master Mode Select to 1 in CTS. This mapping is explained in the User Reference, though I neglected to put it in the VR changes in the HOTAS diagram portion of the documentation. I will update this for the next release. EDIT: Sniped by Kisi! (not really sniped, just didn't see the reply)
  7. No problem, Lorenzo. I'm glad it is now working for you. I'm curious to hear your workaround so I may put it in the instructions.
  8. I can't fathom what it could be. I'll ask the GUI developer if he has any ideas. EDIT: What Unicode country are you using and what language is your OS?
  9. The only other thing I can think of is to install to a completely different path, try again, and run the profile from the CTS EXE itself. If you still have issues, please pass me the dcs_world.tmc from the new folder (just to make sure it's not a legacy file somewhere). CTS doesn't use any registry entries, and it generates its own launcher batch file based on the path it detects. Not sure what else it could be.
  10. @MemphisBelleplease see above.
  11. Version 2.63c Hotfix 3 released for DCS 2.7.14.24228. Change Log: Compatibility updates for DCS 2.7.14 F-14: updated emergency wing sweep functionality Converted TID functions from array to cycle Updated bindings since 2.63b: F-14 Updated SnapViews since 2.63: None Updated Custom Luas since 2.63b: AV-8B, F-14
  12. Building dcs_world.tmc is strictly the job of the EXE using a MS Access database. The version of TARGET should have nothing to do with it. Try deleting cts.db again, then run the installer and do a Full Install to overwrite the old database. Then see if that fixes the issue.
  13. This version also had the variables at the end. Does the compiler not properly put them in their sections? Again, order matters because some values are dependent on predecessors.
  14. I'm curious to hear what happens if you do try to use the EXE to build the file. Are you getting runtime errors with the script?
  15. Sorry I took so long to get back to you. It looks like most of the values were not placed in their sections. The order of some of the values is important. Did you build the profile using the EXE? If so, try archiving your CTS.dat then removing it from your CTS folder. See if rebuilding your data file will fix it.
  16. Updated for QHUD/Target of Opportunity technique.
  17. Version 2.7.120 is uploaded for DCS 2.7.12.23362 (added technicals).
  18. Could you guys please post your dcs_world.tmc files.
  19. Don't know about the first question. Re: intercepting a departure radial, when you do a standard rate turn you will start your turn early to intercept the desired DME arc. Starting your turn at 7 to intercept a 10 mile arc is a very reasonable entering argument. For Case II, that's a hybrid where you have visibility down low, but you're not completely VMC around the boat. It could be cases like broken or scattered clouds where you can see up high through certain pockets, but not enough blanket visibility to have total VMC allowing for Case I.
  20. Excellent post, and the quote above pretty much nails it! Well spoken!
  21. It's been a while since I've reviewed the Huey profile, and something may have changed with the settings. I'll take a look at it. I was just able to update. Is it still down on your end?
  22. I'm always open to suggestions, and especially how to map the controls for the CP/G. I do have the MFDs mapped, and the following reserved: Stick: H1: Chaff/Flare/Station Change H2: Weapons Select (/I SnapViews) H3: George/HMD Select (George selectable with S1 like the Mi-24) H4: Trim (non-negotiable, uses my TCPTM routine) S2: George weapon release auth/take control S3: Tailwheel lock toggle S4: Wheel Brake TG1/2: Weapon (/I Trigger Guard toggle) Throttle: CS: Sensor select Mic: Comms (TBD) Engine Switches: Starter/Throttle Idle The rest is TBD and open for suggestions.
  23. Folks, my apologies for being AFK for a while. This is my busiest time of year IRL. While I plan on putting out a hotfix for the 2.7.11 patch, I don't anticipate having an AH-64 profile until May. If I get some time I may put together a WIP profile, but no promises.
  24. Make sure you assign Buttons 30-32 as modifiers. That's why you have combined keystrokes and joystick buttons in the keyboard diff.lua
×
×
  • Create New...