Jump to content

MOARdV

Members
  • Content Count

    2,092
  • Joined

  • Last visited

Everything posted by MOARdV

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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,
  6. 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 cou
  7. 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
  8. 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
  9. Certainly. If you can add it to the Documents folder next to the other ASET PDFs, that would be great.
  10. 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.
  11. 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 cl
  12. 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 i
  13. No need to apologize. That happens to a lot of us. That RD-0124 looks good so far.
  14. 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
  15. 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.
  16. 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 pr
  17. 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.
  18. EASPEED is effective airspeed. RPM uses the same equation that FAR uses (it was copy/pasted from FAR source).
  19. 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
  20. Yeah, no, I meant the MAS update that patches the RPM ASET props. My bad - I knew what I meant when it was rattling around in my head, but I didn't get all of it typed out. Although there are a few props in the ASET pack that have never been used in an IVA. No configs, or only a sample config was ever written. And I do have an external camera prop that's really cool - the camera housing pitches and pivots in response to commands, so the camera lens is actually facing where the camera is looking. I should totally include that in the 1.3.0 release. I don't think I have the camera mast p
  21. And, for a double post: MAS v1.2.1 is now out. This was originally a bug fix release for the JSI MFD, but @cyberKerb provided a pull request to add some initial support for resource harvesters and resource scanners. Many thanks for that PR!
  22. Heh. I wish. A lot of the conversion work is tedious, and it bores me fairly quickly. That's why I put it off for so long. I hope to have it done by the end of this year, but that mostly depends on how soon I burn out on going though config files and trying to figure out what they're doing. I started on the props for the ALCOR lander so I could test them, and I might have 40% of them done (the MFDs are going to be the killers to convert - it took me a week to get through the simple JSI MFDs). But even the ALCOR pack uses only a fraction of the ASET collection.
  23. When the ASET Avionics/Props update is out, I'll need help testing a lot of different IVAs. There are hundreds of props in the ASET prop packs, and there's no way for me to test all of them. I'm doing what I can, but even the classic ALCOR lander has a few hundred unique props in it.
  24. Yes, that's the way RPM (and MAS) does it, by looking at the vessel description. You can also be fancy with it and use AG5=doohickeys on|doohickeys off to make the action group label change depending on if the AG is "on" or "off".
  25. @JonnyOThan was kind enough to let me advertise this on the RPM thread. The IVA mod I've been working on for the last couple of years now has an update that replaces the basic RPM props with MAS-enabled props. If you're using any of the IVAs that are included in the core RPM distribution, and you install MOARdV's Avionics Systems, MAS will power the IVA. A future update will support ASET Avionics and ASET Props as well.
×
×
  • Create New...