Jump to content

linuxgurugamer

Bug Hunter
  • Posts

    24,965
  • Joined

  • Last visited

Everything posted by linuxgurugamer

  1. Agencies don't fo anything, other than gameplay Find an existing agency and look at the file. Spaxetux industries is one that is mine, feel free
  2. Take a look at the landing height display mod for some good code to do that, may be helpful
  3. Glad its working for you. In the future, when you have a problem with a mod, please post in that mods' thread. If no mods were showing with the toolbar controller, then it would have made sense to post here, but it was a single mod, and there were already posts in the thread about this problem
  4. You need to add an instruction manual : Flying Saucer Flight Operations to the scene. Maybe even clicking on it would bring up the Kspepedia (?) page?
  5. Correction The icon is there, it's just all white The icon in question is: saucerTech.dds
  6. New release, 1.3.5.2: Updated to latest ToolbarController Removed blizzy option, now handled by the ToolbarController Added dependency checking
  7. ToadicusTools is used by the following mods: AntennaRange IR-Model-Rework-Utility TweakableEverything VOID and of course, I forgot the download link. Here it is: https://spacedock.info/mod/1069/ToadicusToolsContinued Also in CKAN
  8. @Angel-125 Just got my first start with this. Got a tiny little bug: I unlocked all technologies as a test. In the R&D building, the icon for "Saucer Technologies" is missing Let me know if you need anything else, IMHO I don't think you need a log file for this edit: See followup post below
  9. New release, 0.9.7.1: Fixed race condition where sometimes the toolbar was being created before it was registered, causing it to not show up A short explanation is in order here: First, a definition (from Wikipedia): What happened is that in my testing, it worked fine on my system, in my test environments. What I didn't realize is that there were two classes which were being instantiated at the same time (at the MainMenu), one of which depended on the other to be completed. So sometimes one completed first, and sometimes the other completed first. This is totally random, although it can be influenced by many unknown factors. This is why it was working for me, and not for other people. Once I saw the reports, I created a clean install to test it, and was able to replicate the problem about half the time, That gave me something to work with, and I was able to track this down and fix it.
  10. I have been able to confirm this problem, working on it. so far, no idea what's going on
  11. Being polite can go a long way. Sorry, it was late and I was tired with a headache. Ill look into this tomorrow morning. In the meantime, please post a log file, in the correct thread; ie: the RCS Build Aid thread Also, there was a bad release I had to delete, it sounds like you might have gotten that one I've been able to confirm this, will only be responding on this subject in the RCS Buildaid forum moving forward
  12. I dont know about the pause, but it only shows science currently available
  13. Did you look in the ToolbarController window (the yellow wrench) to see if it is enabled?
  14. Just a guess, how is the health of the hard disk drive?
  15. There is an amazing amount of code which can be eliminated by using the toolbar controller, I started wo t.f king on it today
  16. Have you verified that the controller works and is visible ? Stupid question, but I need to ask. I'll see about a debug build, but it really sounds like it could be a driver issue
  17. Its fine, except I already have an OSX build, was there something missing? I will have to make an Arch Linux install to test this, is going to take a while
  18. How about: IGNORE_OVERRIDE = modname And I can include a list of mods shich should be ignored.
  19. @jefftimlin @DennyTX This mod is very useful and should be updated for 1.4. If there isn't any objection, I'll be working on adopting this and updating it for 1.4, as well as adding support for the toolbarcontroller and clickthroughblocker. By using the ToolbarController, the user will have the option as to where to put the button, and will remove any complex button logic from the code
  20. Working on the final syntax now: KSP-AVC { // OVERRIDE_PRIORITY authority; will override anything in any of the .version files. This includes any of the // simple overrides in the files // OVERRIDE_PRIORITY has the following possible values // remote remote file overrides local file // local local file overrides remote file // none local file overrides remote file OVERRIDE_PRIORITY = remote // SIMPLE_PRIORITY has the following possible values: // remote remote file has priority over local file // local local file has priority over remote file SIMPLE_PRIORITY = remote // SIMPLE_PRIORITY can allow an individual .version file to specify which file should have priority. // This will allow one of the following lines in a specific .version file will take priority: // "LOCAL_HAS_PRIORITY": true // "LOCAL_HAS_PRIORITY": false // "REMOTE_HAS_PRIORITY": true // "REMOTE_HAS_PRIORITY": false // KSP-AVC now can be configured to automatically allow // multiple KSP versions to be compatible with other versions (see below) // This would be in a .version file to explictly say that this override // is not allowable for that specific .version file // "DISABLE_COMPATIBLE_VERSION_OVERRIDE": true } A new feature will be this: // This would be in a separate file, to be created by the user. This is entirely optional // and is intended to allow a user to tell KSP-AVC that, for example, all mods which are // listed as compatible up to version 1.4.1, would also be compatible with 1.4.3, etc KSP-AVC { // This tells KSP-AVC that any mod with the first version listed is also compatible // with the second version on the line COMPATIBLE_VERSION_OVERRIDE = 1.4, 1.4.3 COMPATIBLE_VERSION_OVERRIDE = 1.4.1, 1.4.3 COMPATIBLE_VERSION_OVERRIDE = 1.4.2, 1.4.3 }
×
×
  • Create New...