Jump to content

MOARdV

Members
 View Profile  See their activity

  • Posts

    2,173

  • Joined

  • Last visited

 Content Type 

Everything posted by MOARdV

  1. MOARdV
    That's likely the problem, then. The PR he provided with the props included an IVA, so they may be colliding with each other. Without a log, though, all I can do is speculate. The other things you could do are remove either the IVA config patch you already have or the one that's included in MAS for that cockpit.
  2. MOARdV
    On Windows, at least, it's a file called KSP.log next to the .exe that launches the game (one directory level above the GameData directory). IIRC, there's a link in my sig to the forum post about where to find it. If you can put that text file on a file sharing site and give me a link, I'll be able to dig through it and see what's going on. Where did you get the OPT-J IVA cabin? I wasn't aware that the IVA was released outside of the one included in the vulkans's pull request.
  3. MOARdV
    As LGG said, it was to avoid breaking existing craft that used the old lights. On the other hand, they were deprecated over three years ago, so maybe it's time for them to go. That's a good idea. I remember there was a tutorial somewhere for how to go about creating kspedia pages, but it looked fairly convoluted. I'll open an issue so I don't forget when I have more time for modding.
  4. MOARdV
    Aviation Lights v4.1.2 is now available on GitHub. This is a minor update that adds a Brazilian Portuguese localization courtesy of @Lisias. Currently, I don't have any plans for new features for this mod since it does everything I want it to do. Are there any features anyone thinks need to be added? I had thought about allowing the aviation lights to be connected to the axis controls that KSP introduced several versions ago, but that doesn't feel like a good match in functionality.
  5. MOARdV
    MAS v1.2.3 is now available on GitHub. This release adds many new ASET Avionics props courtesy GitHub user vulkans22, a new example IVA for the OPT-J HT cockpit (also by vulkans22), and a handful of prop config fixes. As of this update, there are a few ASET Avionics props that need converted to MAS. There are still a lot of ASET Props that need updated, and a couple of MFDs. The DLL version was updated, but there are no functional changes to it - this release is primarily so IVA developers have access to more MAS-enabled ASET props.
  6. MOARdV
    That patch is only going to replace the 'map' on the Globus / IMP instrument (the device that's based on the old Soyuz IMP), unfortunately. The MFDs are all 'hardcoded' to use the Kerbin map. I think a patch for the MFDs would look something like MAS_PAGE:NEEDS[JNSQ] { @IMAGE,*:HAS[ (this part I don't remember how to write - I haven't written fancy patches in a LONG time) ] { @texture=MOARdV/Patches/JNSQ/map_JNSQ_sat } } Obviously, the important part of that patch is the part I don't remember how to write. It needs to select all IMAGE nodes that contain "texture=ASET/ASET_Props/Instruments/ASET_IMP/map_Kerbin_sat" and replace it with the path to the JNSQ map. What I really should have done is make the MFD map configurable in the flight computer modules. Maybe when I can get back to modding again, I can address that ... Hmm, I better write up the issue on GitHub so I don't forget.
  7. MOARdV
    Everything is proceeding as I have foreseen.... I kid. But I am enthused about the prospect of having that size gap filled by this mod when I finally have a chance to revisit KSP to play for a while.
  8. MOARdV
    I removed the Yarborough IVA about 3 years ago, since the pod hadn't been updated in a long, long time. If you download an old version of MAS and extract only the Mk1-2 IVA files to use with a current version of MAS, it *may* work, but I can not promise that it will. If I ever have the time to work on IVAs again, I may try to update the Yarborough pod IVA, since it was one of the better designs for IVA that I've found.
  9. MOARdV
    No, none of those MAS-enabled props were released anywhere, as far as I know. I have an external camera part somewhere around here that was designed for MAS that will pitch and yaw based on the camera settings, but none of those awesome MAS-ready props ever made it into the wild.
  10. MOARdV
    I have never seen that happen, although I'll admit I've spent maybe 15 minutes in 1.11.0, and I don't think I've started the game with 1.11.1 . That's really weird, since it looks like that's during loading. Oh, wait. I've got a couple of GameObject classes that are new'd where they're declared in that class. I just double-checked the log I have from 1.11.0, and it's not showing an exception, so that's perplexing. Addendum: I just relaunched with 1.11.1, and I still don't have those exceptions showing up. I'm not sure what's going on.
  11. MOARdV
    Sorry, folks. Real Life has been plenty busy. You can use the Lua trig functions, currently, as you're aware. They are slow. I didn't override them with faster proxies, although maybe it's time I did that. I'll add a reminder on GitHub for whenever I have time to spend playing around with KSP and MAS again. It's been a while since I looked at the Kane IVA, but back when I did, it was not a good one for IVA layout (I don't remember exactly why, now - it's been too long ). The FASA IVA was a good replica of the Apollo interior, but I couldn't substitute it for the BDB IVA, because it didn't match up with the shape of the pod. It wasn't an ideal solution (I'd rather not require additional parts and internal models), but it was more important for me to get an IVA configured the way I wanted, and I am definitely not a 3D artist, so I couldn't create or modify my own. It's hard to find an IVA that is well-designed for complex instrumentation. Or maybe I'm just too picky about how I want the interior configured.
  12. MOARdV
    Yes, that's exactly why that condition is set up that way. Under normal circumstances, there's no reason for MAS to spend time during the game loop to compute vessel-wide values and update props if no Kerbal is there to see it. Likewise, probes don't have IVAs. Unless you're using ProbeControlRoom, that is. The only reasons I'd be reluctant to change that are: First, I don't use ProbeControlRoom, and I don't want to have to chase PCR-specific bugs if they crop up. Second, I don't want to impose any performance penalties on players who don't have PCR installed. That said, MAS could detect if PCR is installed, and ignore the vesselCrewed test if it is. Please feel free to open an issue on GitHub. I won't make any commitments on when I'll get to it, since I've been away from KSP for a few weeks. But at least that way, I'll have a reminder when I do have time for modding again.
  13. MOARdV
    It's not really a lot to ask. I don't think I hooked up the KER suicide burn stats. The landing page on the MFDs could stand some updates - I designed it for a "traditional" capsule that uses parachutes to slow descent, and not a powered landing, since I rarely leave LEO. I've added a note on Github to remind myself to add the KER stats. I don't know when I'll get the MFDs updated - what I really want to do is work on a touch screen MFD, but I need to plan it out first. Usually, I get an idea of what I want to do, start making pages for it, and then run out of ideas and leave the MFD incomplete.
  14. MOARdV
    MAS already has a patch to do that - MAS_mk1-3.cfg in the MOARdV/FlightSystems folder. I'm not sure why it didn't work (although I haven't had a chance to look at the log yet to see if it ran - work has been really busy lately). Although maybe I have something messed up with the MM patches in the last release.... Oh, wait. The last round replaces JSI props with MAS props in IVAs, but I don't have an MM patch to add the MAS Flight Computer to all the command pods . So, yeah, I do have something messed up with the MM patches. Sorry about that - you can add a patch like @Manul suggested, or you can disable the MAS patching by renaming or removing MOARdV/Patches/JsiToMasUpgrade.cfg
  15. MOARdV
    Certainly. If you can add it to the Documents folder next to the other ASET PDFs, that would be great.
  16. MOARdV
    And I've got Aug 22, 2017. Yeah, I'd like to have the latest one, in case there are some changes in there that MAS needs to account for, please. And so I can put it in the GitHub documents folder.
  17. MOARdV
    Either of those are higher than *my* estimate. I know I've got the PDF, but I've never seen the source files. I know @alexustas and I discussed them once upon a time, but Real Life had become rather busy last time I talked to him. I'd be amenable to a common data format, as long as it can support the information MAS needs to accurately simulate radio navigation. That would be incredible. I would love to get the MAS props complete enough to really show off what they do, and how much better the player experience is because of the under-the-hood changes. I was >< this close (well, maybe >---< that close) to wrapping up the ASET MFDs, which would allow MAS to fully support the ALCOR lander, and possibly quite a few other IVAs. There's definitely a down side to Alexustas having made so many props - they provide an incredible variety of style options, from 1960's tech to modern, but it means that there's a lot of work involved making conversions. Especially the MFDs - I managed to get about 1 1/2 of the 3 MFDs update before I had to take a break. The video is cool - seeing the radio nav stuff functioning is awesome. FWIW, MAS enabled the entire kOS terminal prop (the one with the full keyboard below the screen). I mapped out all of the colliders to softkeys, so MAS could possibly interact with kOS at a keyboard input level.
  18. MOARdV
    Howdy, folks. I've pushed MAS v1.2.2 out on GitHub. This release is partially a bug-fix release, and partially an ASET prop conversion dump. I've done a very cursory 1.11.0 test, and the suborbital Mk1 IVA seems to be working. YMMV. With this update, all of the Classic RasterPropMonitor props (the ones included in RPM) are replaced with MAS props. There is also an optional patch that converts some ASET RPM props to ASET MAS props (a few hundred props are converted - which is less than half of them). If you enable that latter patch, most of the ALCOR lander IVA will use MAS props instead of RPM props - the only prop that is still an RPM prop is the "kOS Terminal" prop with the keyboard. The release notes tell you how to do enable that patch, for the adventurous. Thanks to @theonegalen for the ASET Avionics conversions in this release, and to user vulkans22 on GitHub for the bug fixes.
  19. MOARdV
    No need to apologize. That happens to a lot of us. That RD-0124 looks good so far.
  20. MOARdV
    IVAs take time to build - the simple IVAs might take someone a few hours to put together, depending on how familiar they are with the tools. The reason I never updated the basic IVAs while I managed RPM was that I never used them, and I really wanted to showcase the far better props available in alexustas's ASET props sets. Fortunately, all of the tools are freely available, so anyone can download and install them to make IVAs to their own specifications, as simple or complex as they may want. You may even give it a try, and if you come up with something you like, you could submit it to JohnnyOThan to add to RPM, so everyone else may enjoy it as well.
  21. MOARdV
    What in-game diameter are you going to use for the URM-1? I assumed it would be 1.875m, since I think that would be about correct for KSP scaling.
  22. MOARdV
    Hey, all. I thought I'd provide a road map for MAS going forward. Starting with MAS v1.3.0, the ASET MAS update patch will be enabled by default (on purpose, not by accident like v1.2.1 ). MAS v1.3.0 will include updates for all of the props used in the ASET ALCOR Lander, along with any other props that have been updated. If you do not want to use the MAS prop updates, you will need to delete the Module Manager config file. What I will need is players who will use the MM patch to try various IVAs, understanding that the update is not 100% complete. I've updated hundreds of props, and it is very likely that I typed something in wrong or missed some detail. If you are willing to help beta test the MAS update, please submit bug reports - preferably, with a screen shot so I can try to identify which prop is configured incorrectly. When the ASET RPM conversion is complete and I've gotten some feedback on it, I will bump the MAS version to v2.0.0 and call it a full release.
  23. MOARdV
    In RPM, there isn't a "greater than". You have to set the upper range to something absurd, like 100000 (for atmospheres). That's one thing MAS fixes.
  24. MOARdV
    EASPEED is effective airspeed. RPM uses the same equation that FAR uses (it was copy/pasted from FAR source).
  25. MOARdV
    As a head's-up - it looks like I forgot to rename the ASET update patch in the 1.2.1 release, so you're going to see a partial replacement of props by default. I'd recommend deleting GameData/MOARdV/Patches/AsetToMasUpgrade.cfg, unless you want to guess which props are RPM and which are MAS
×
×
  • Create New...