Jump to content

Stone Blue

Members
  • Posts

    5,100
  • Joined

Everything posted by Stone Blue

  1. @alexalex should be... look at some of the MechJeb cfgs... Pretty sure Mechjeb allows setting tech unlock/upgrades on certain functions on the mechjeb parts
  2. yup... I hate when peeps use direct/deeper links, than just to the Releases page (/releases/).... do *that*, and you are guaranteed users *always* get directed to the most current release... and saves having the dev to go back & update OP *every* time they do a release to keep the link current.
  3. Very nice!! Hmm... this might be a good candidate to have as an in-game, IVA checklist, too Off the top of my head, it could be done using images of each page, with this MAS/NearFuture prop: Or, it could also be done using images, *or as a .pdf*, with this in-game mod:
  4. oh! I forgot...you wanna use this in an existing IVA, prolly no, dont mess with this cfg at all. All you have to do, is open the cfg of the specific monitor you want to replce it with, to find out the actul name the game uses for the monitor prop, (the "name =" field), in this case, for the default ALCOR MFD, its "MAS_ALCOR_MFD40x20" (without quotes). Then open the .cfg for the specific IVA you want to do the replcement in. Search/find the PROP{ } module that has that name. Then just replace the name with "MAS_APEx_MFD40x20_kOS" (without quotes). That should do it. *HOWEVER*, i forgot to tell you you need one moar file, also https://github.com/StoneBlue/AvionicsSystems/blob/New-Vulkan-M2X-APEx-Angler-Props/GameData/MOARdV/MAS_ASET/ALCORMFD40x20/MFD40x20/MAS_APEx_MFD40x20_PG_kOSPropMonitor.cfg you dont need to do anything with this file, either, other than to make sure it goes into the folder included after the /MOARdV/ part of the link. *AND*, IIRC, you need to install the kOS PropMonitor mod, too.
  5. Lmk know, here on this thread, if theres any problems with that kOS MFD cfg I posted in the BakerOS thread, please.
  6. Its here, in my fork of MAS, waiting for a PR merge from MOARdV: https://github.com/StoneBlue/AvionicsSystems/blob/New-Vulkan-M2X-APEx-Angler-Props/GameData/MOARdV/MAS_ASET/ALCORMFD40x20/MAS_APEx_MFD40x20_kOS.cfg Makke sure you put it in the same folder as listed in the end of the link
  7. Kewl mod Just wondering why you have .tga's in the CYLINDERS folder? the mod is just shy of 1GB... you could probably shrink that significantly if you convert to .DDS textures
  8. @linuxgurugamer I dont know if youre aware of these, and if it would help to look at them or not, but they are also attempts at KSP multimonitor support. Sounded like Sarbian came close, but Unity multimonitor support was new, & lacking at the time (Unity 5.x)... Said they were hopeful a newer version of unity with fixes might be worth coming back to revisit the attempt vOv
  9. Easy enuff... *possibly*... Try copy/pasting the MODULE{} & RESOURCE{} sections of the cfg, into whatever *other* part config of the part you want to enable this for. If that doesnt work, then there may be something part-specific hard-coded into the plugin... (I *hope* thats not the case)
  10. @jay chou its also generally frowned upon, to have spaces in folder names
  11. I could be wrong, but I dont even think you need TM Pro, if all you are making is parts or IVAs. IIRC, you really only need it if you creating a GUI for a plugin. vOv I have been using Unity without it for a few years.
  12. No one *can*... unless they get explicit permission from @mcdouble, or mcbouble makes a new release with the addition of a more open license... Right now, this has *NO* license stated (which is technically against forum rules), so it automatically falls under an assumed ARR (All Rights Reserved) license... which is an absolute closed license.
  13. @ParaYouKnowWho heh.. dont sweat it... happens to the best of us... *especially* with non-CKAN/manual installs
  14. OH!... gotcha.. I thought it was simply the *camera view* aspect... didnt know there was other *stuff* being asked about/involved.
  15. Looks lie you dont have Toolbar Controller mod installed. Its a required dependency for ClickThrough Blocker... among many other mods. You have TONS of problems in your install. I would install Toolbar Controller, and if the issue persists, post a new log (at the least, adding TC should get rid of a LOT of stuff in your logs)
  16. At the least, if you have basic modelling knowlegde, you could probably just create a model, that is just a simple parent object, & a childed camera transform, placed to match specific external cockpit part models, and add your simple model to those relative cockpit parts, with an MM patch, then add a module in another MM patch, to the relative MFD prop cfg. Basically, its making an external camera part, like those in HullcamVDS, or even the integrated external cameras in the ASET ALCOR pod... *just without any external skin*, and also not having to actually place them as parts in the editor
  17. Uhh... IIRC, that *should* be relatively easy. I imagine the mirror just has a rear-ward facing camera transform... Should be able to whip up an MM patch, that adds that transform to the camera pages on any MFD vOv
  18. Yeah.. i saw the mention about the repo sync Was just wondering, cuz i wanted to have the code source files, but didnt want to have to download the extra 1.8GB of the seperate texture .zip, if it was the same as in the master if they'll be the same from now on *after* you resync/organize the repo... i can wait till then
  19. So I ass-u-me if I download the repo master, (which has a stock textures folder) in it... then i do NOT have to also grab the Stock Textures zip seperately?
  20. @DaveyJ576 youre getting there.. just need one more braket at the very end of the cfg... should have four there, not just three
×
×
  • Create New...