Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. I recently had this issue. I figured it was because I started the Tomcat from a land base, but apparently if it happens in Raven One this isn't that specific an issue. That said, happened here too.
  2. Version 2.7.11 is uploaded for DCS 2.7.1.67090
  3. Version 2.57 is uploaded. Big thing is the new T-45 profile, along with 2.7.1 compatibility.
  4. Version 2.7.10 is uploaded for DCS 2.7.1.64300
  5. Thanks, and to you as well. Right now I'm very busy with RL, and after that I have a lot of work on my plate for updating CTS. Skins are taking a back seat for the time being.
  6. If the description.lua files are conflicting, those cannot be changed without messing up the skin. You just need to make sure they're nested in different folders, or if they are the same skin then remove one of them. For example, if you have a skin "F-14 VF-32 101" and "F-14 VF-32 102", both will have a description.lua file. However, if the folders both say "F-14 VF-32", you will need to rename one of the folders so the description.lua files are deconflicted (and both skins will show up).
  7. If it's overlapping description.lua files (assuming this is the lua file it's overlapping), then somewhere you have a folder/skin with the same name in two different mods. description.lua is in every skin folder; this is the file index for the skin itself. There's no big mystery to the JSGME/OVGME framework. If you dig down into the mod itself, you will see the nested file structure identical to the structure within the DCS World install. Or at least it should be identical. This is where you want to check to see if perhaps one of the folders is missing, misnamed, or nested improperly. Unfortunately, if you don't know which specific file is being duplicated, there is no easy way to do this. You just have to look in the file structure in the mod and find the incorrect folder or file placement.
  8. It totally depends. OVGME is a generic mod manager, and it only tells you when it is overwriting a modded file with the same name. It could well be that the textures are identical (perhaps mod packs from the same author), or they could be different. FWIW, if they're my skin packs and you installed them using the JSGME method, the shared files with the same names are identical. That said, I consider it a better practice to install your skins to your Saved Games\DCS folder. Create a folder called Liveries under Saved Games\DCS, then copy the skins to your new Liveries folder starting with the Liveries\Aircraft filename. For example, if you're moving a F-14B skin, you would move the CoreMods\aircraft\F14\Liveries\F-14B folder containing those skins to C:\Users\Username\Saved Games\DCS\Liveries\F-14B which includes all the skins in the subfolders of F-14B. Hope this helps.
  9. Working on it, but no timeline since my RL work schedule is still crazy.
  10. Version 2.7.00 is uploaded for DCS 2.7.0.51180.
  11. There's no uninstaller because there are no registry entries for CTS. You can just delete the CTS folder. That said, I can't see how CTS itself could cause issues with your hardware. It works within TARGET. There may be certain options you can enable to make the profile more (or less) stable, but that is different from causing issues with the hardware. Also, 2.56a (Hotfix 1) is now up. It updates the AV-8B Custom LUA and the P-51 diff.lua for DCS 2.7.0.51180.
  12. Version 2.56 is releaed. Change log: Updated all profiles for DCS 2.7.0 AJS37: Added Autopilot buttons to H2 Long. AV-8B: Fixed bug where the nozzle stop would keep moving after CH was released. MiG-19: Synched bombsight depression commands on CS and H3. M-2000C: Updated INS/Engine Start bindings to a more logical layout. Added Air Starter to S3+RCON (GSU). Added Combined Selective Jettison functionality to LBRT.
  13. Thanks for the heads-up @MrArsGravis. I won't be updating the IL-2 profile in the current version of CTS anymore because I have already removed it from a future version and created CTS for Windows (which will support other games). This is to free up stack space for upcoming DCS modules. Once I get CTS for Windows into a public beta, I will remove IL-2 and Elite from the DCS profile. I don't recall if I changed THR_FC back (the Thrustmaster implementation of the mouse is buggy and I don't like to use it), but I will definitely keep this in mind when I can get back to working on CTS. With my current work schedule, this is unlikely to start before June. I will, however, post your content on Trello, though it will be for the new CTS version. Only thing I can think of is the database has become corrupted. Even reinstalling CTS will likely pull in your old settings if you didn't delete the CTS.dat file (which is the file that stores your settings, and is dynamically updated each new release). Try backing up, then deleting CTS.dat. Then run CTS.exe and it will act as if you are running CTS for the first time. Then set your values (and TrackIR should be set to 2 for VR).
  14. Sorry for not responding sooner; my work schedule has been absolutely insane. There are four zip files within the zip file you download from User Files. Extract these zip files to your OvGME Mod folder. OvGME will be able to read those zip files. One of the zip files is the "master" file that contains all of the updated graphics. Enable this. The other three files are mutually exclusive, and you select which one you prefer (e.g. USN instead of USAF Adversary, USMC instead of USAF Adversary, or just the general update). So you should choose exactly two mods (zip files) to enable this.
  15. Someone else reported that they were blocked from the UK, but were successful with a VPN using a Seattle IP. I won't have time to check the firewall settings for some time (it's a new system that was an emergency replacement of the old one), so you may wish to try this. If you are using a USA-based IP and it still doesn't work, please let me know.
  16. True, which is why calling it may point to something else. It's why I was asking if the issue could be duplicated.
  17. Hmm. It's calling the TARGET header file in the error, so it's difficult to say. Can you duplicate the error using the same module/key command?
  18. This, and it's considered a best practice to put anything you can in Saved Games rather than modifying your main install whenever possible.
  19. If all is working properly, the Thrustmaster peripherals that are called in the TARGET profile should disappear and be replaced by a "Thrustmaster Combined" device (Thrustmaster Root if you're using an Admin account). Sometimes the Warthog stick and throttle will still show if the Microsoft Store is in RAM, but this is not a desirable outcome. Unless you're referring to a stick going stupid when the profile loads, in which case you should stop the profile, unplug/replug the stick in the USB port, and re-run the profile. I get that occasionally and I attribute that to the USB hub.
  20. That feature will be (somehow) implemented in 3.0.
  21. Both should be fixed in 2.55. If not, what HOTAS are you using?
  22. Thanks for the heads-up on that. I'm not sure where the issue lies, but the new router is only a few weeks old. Glad you got it sorted, though.
  23. Were you able to download CTS previously?
×
×
  • Create New...