Jump to content

Stone Blue

Members
 View Profile  See their activity

  • Posts

    5,100

  • Joined

 Content Type 

Everything posted by Stone Blue

  1. Stone Blue
    Huh.. too bad this mod seems to have dropped by the wayside very quicly... Sounds interesting. I wish there was moar discussion, and pics, in thread about exactly this mod did.
  2. Stone Blue
    Unfortunately, @gagarinekerman 's sorce code link no longer works, but it seems @Thomdare may have thrown a version up on Github, HERE, just in case anyone evere wanted to try to revive/adopt this mod. vOv
  3. Stone Blue
    And this is why its always nice to have access to the source code on every mod
  4. Stone Blue

    Hi
    I saw your post on MAS, about Probe Control Room.
    I've been working on a PCB IVA, also with MAS props. I was wondering if you would care toshare your .dll with me.
    I promise not to distribute it.
    I've been in contact quite a bit with MOARdV in the past, about both RPM and MAS.

    If not, no worries. :)
    Thanx
    Stone Blue

  5. Stone Blue
    Umm... I may be missing exactly what KIFA needs, but I'm not clear on why IS pasrt *shouldnt* NEED IS to be installed? vOv As to this, PLEASE mae sure your changes NEVER get publicly distributed. That may be a couple ways to do it, but those will really mess up someones install if they do have/try to install KIS. Also, not sure if adding empty .cfg files freezes/crashes the game anymoar. I know it used to... vOv Your over thinking it. To address this, (and this is for each user's install, ONLY when KIS is NOT installed, and ONLY for *personal* use (shouldnt be distributed)), is to just change any :NEEDS[KIS] in any patches, to :FOR[KIS] This basically tells MM to *assume* the KIS folder is there...w/o it really being there... Doing this, will also negate the need for your 2nd option. AGAIN, :FOR[] usage in patches should ONLY be distributed within the specific mod it is targeting, and only by the official dev/maintainer of said mod. If used improperly, distributed :FOR patches can really brea/screw up people's installs, and cause unecessary headeaches for mod devs, when peoplpe go to them looing for support.
  6. Stone Blue
    For me, manuevering in space EVA. the kerbal backpac RCS controlls are soooooo un-intuitive, combined with the default camera orientation settings. I wish they had just used the same keys for craft RCS, or done something different w/camera orientation... vOv Also, I cant spaceplane worth a damn.
  7. Stone Blue
    No... Why does it *NEED* updating? Does it not work in 1.10 or 1.11? A user just posting that a mod needs to be updated, for no good reason, other than for the author having to constantly say its working/ok to use in current/future updates of KSP, makes no sense, and is quite irritating to mod authors. If a dev has not been active recently, and has not explicitly stated that a mod still works, it should be up to the user to do at least some basic research, like reading bac in the thread to see if others have had problems, or success, with using the mod in newer versions than is explicitly stated by the dev. Or, I dont now, maybe even *trying* it for themselves, to see if it works or not? Its not like you cant run multiple, seperate installs of KSP at the same time. Just install a fresh copy, and try the mod (and any dependencies) in question, see if it works... if it does, install it into your important save game install, and delete the test install you just made... If not, then report whats not woring in the thread, and *then* mebbe inquire about an update... vOv
  8. Stone Blue
    @Mallikas is that your *actual* IVA internal cfg, or a seperate *patch* for your IVA internal cfg? cuz in either case, your missing stuff... the difference is *what* you are missing for each case. So, youre talking about adjusting the Kerbal eye-level/first person camera? And NOT the external camera views? if so, I think that does need to go under the InternalSeat module, which should be in your base IVA cfg. Theres a JSISetInternalCameraFOV module where you can adjust the field of view. Looing at it now, I'm not sure if MAS needs/uses that JSI module or not. Cuz I have it in one of my MAS IVAs. vOv You may also need an InternalCameraTargetHelper module in there, too. I'm not sure what this module does... but it was in a MAS IVA I used as an example to build mine. vOv
  9. Stone Blue
    Which version did you install? for 1.8.1, you should download v1.13.0. v1.14.0 was recompiled for KSP 1.9.0+, and the way KSP handles the camera(s), was changed in 1.9.0... so most liely v1.14.0 is NOT bacward compatable.
  10. Stone Blue
    @Pipcard if you are on KSP later than 1.7.0, you should be posting on the new thread for this mod... NOT this thread You will mmost likely get better support, there. Also, that is the thread for the exact version you downloaded from that Github link you posted.
  11. Stone Blue
    Unfortunately, I wouldnt hold your breath... lol
  12. Stone Blue
    Hmm.. I certainly am no expert on MM patching, but I see vector related errs in your log snippet, and looking at the patch, I see these lines, and I have never seen MM patching a vector with this method: @node_stack_top[6] = 0 @node_stack_bottom[6] = 0 *If* specifying just one part of the normal node attachment key wors lie that, looing at it, I assume you are trying to edit the *size* portion of the node? if so, would that not be `[7]` instead of 6? the 6th element is changing the Z direction of the node, NOT the size, which would be the *7th* element vOv EDIT: @DialoMalison so, yeah, i just got confirmation from someone moar MM experienced, that that edit for the attach nodes should work... so, yeah, what I said about the 6th & 7th positions holds: 6th position is for the Z direction of the node... 7th position is what you want for the *size*
  13. Stone Blue
    Yeah, what Snark said... Usually a screenshot of the *contents*, showing all the folders in there, is sufficient. And the first, and last err look lie they are related to BDB, specifically. Chec the Bluedog thread OP, and make sure you have any required dependencies installed, that you may be missing.
  14. Stone Blue
    No... those are to use as tool for people *making* IVAs... not needed at all for users. But that brings me to another question: where did you download MAS from? If Github, mae *sure* you grab the release .zip from the releases page, and NOT from using the green "Download" button on the main page of the repo... nor the "Source.zip" from the releases page
  15. Stone Blue
    First, what version of KSP are you on? Also, what version of RPM? and is it the *original* RPM, or RPM Adopted? Second, what IVA are you having trouble with? Third, best to post a link to your *whole* KSP.log. Use Dropbox, OneDrive, GoogleDrive, etc. DONT copy/paste the whole log in the thread. It initially looks like the IVA may not be set up properly. Thats why it needs to be known whether this is an issue with an IVA mod, rather than MAS itself.
  16. Stone Blue
    WoW.... this is a huge update... THANX for all the work and effort, Dunbaratu
  17. Stone Blue
    Good to know. Are you *on* 1.8.1? even if you are, might be good to install RPM Adopted. JonnyO adopted it sometime after 1.8.1 released, but before 1.9.1... So, both the original RPM, and his Adopted version both work in 1.8.1 (at least the first release of Adopted (not sure about subsequent ones))... so might be good to try RPM Adopted anyway
  18. Stone Blue
    Not sure if this is *exactly* for Station Science, or relevent: https://github.com/KSP-RO/RP-0/blob/master/GameData/RP-0/Science/Experiments/StationScienceEarly.cfg Have you gone thru any of the RO forks on github (I know, there are TONS of them ) , to see if you can find anything specific to Station Science? vOv
  19. Stone Blue
    @iGGin I dont remember exactly what this mod does, or why it existed. However, if you read the OP, it seems to *replace*, or at least modify RPM. I dont see off hand, any difference in the MFDs from the screenshots in the OP, to the current version of RPM. I would remove this mod, and then install the current version of RPM Adopted, from this link. See if it does everything MFD Revived does. and an FYI for @JonnyOThan ... As I said above, I dont remember exactly what this mod does... I dont know if its already been integrated or whatever into RPM at some point, but i figure you would be the best person to look and see, and if this mod has some features NOT in RPM at this point, and if it *does* have something worth while that RPM doesnt, mebbe look and see if it is worth integrating? vOv
  20. Stone Blue
    Oh!.. you know what? @KyZeNickX I derped... you are also missing Community Resource Pack, which may be a dependency for OPT Reconfig... which might explain the probable resource issue B9 is screaming about. IIRC, Jade recently made a change, where CRP may *not* be reuired for OPT Reconfig anymoar... Hmm.. I was also under the assumption that Nert's mods needed CRP as a dependency, also, but I dont see it in the SSPXr OP. But I would say that that right there could also be your issue, since this started right when you installed SSPXr (barring a too-old-unsupported version of an OPT mod/MM). Even tho CRP may not be a *required* dependency for either mor, there may be some stray patch somewhere, that only rears its head when *BOTH* an OPT mod *AND* SSPXr, *AND/NOT* CRP are installed... vOv After you verify all your mod versions, I would then try installing CRP if the issye goes away. If it indeed does, then JadeOfMaar definately needs to know. He'll also know if Nertea also needs to be aware of this.
  21. Stone Blue
    @KyZeNickX You have a conflict with something in one of the OPT mods. Looks like an OPT issue with either an ATM (mebbe something related to an "atm"osphere or resource thing)... Make *sure* you have all the appropriate versions for all three OPT mods, for the appropriate version of KSP you are on. Also, chec your ModuleManager version... v4.1.4 has been current for the last few version of KSP for awhile. I would say it *could* be a conflict with Firespitter, but @JadeOfMaar has worked hard to remove Firespitter support and conflicts from OPT. (Hence, one reason why I suggest verifying you have up to date versions of all the OPT mods) But Jade would be the best person to address your issue. Especially if it *is* a legit issue with something in OPT. And, yes, please follow the instructions in that thread that VoidSquid posted, and post your logs, as well as your ModuleManager.ConfigCache file. It seems pretty huge, considering how few mods you have installed.
  22. Stone Blue
    Ok.. i'll get a PR done
  23. Stone Blue
    @linuxgurugamer sorry it took so long... Considering the function of the part, how about aircraft black box-alike, orange-ish? I could tone doen the color a little moar... it does seem to be not as, bright, in flight scene, tho... vOv I kinda wanted to stay away from existing battery/sensor yellow... vOv But its up to you
  24. Stone Blue
    If its with ReStock, could mebbe be an issue with ReStock using a depthmask on the intakes? vOv
  25. Stone Blue
    Previous release was 1.10.1 ONLY, wasnt it? Is compat for this new version 1.10.1+ *only*, or 1.11.0+ *only*?... or does it include support for, like 1.9.1/1.8.1? Sorry for asing.... if it *is* either, mebbe add that to the changelog? vOv As Always... THANK YOU for the update
×
×
  • Create New...