Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 Ok, now that I got a moment, (Alternating between sick, busy, fretting over the complete insanity happening in my country and too annoyed with KSP.) let's deal with the whole mess in order...I'm sorry for not answering every request and question, everything that's already implemented and is a matter of configuration is getting ignored. Most of the standard grey-screen problems are installation related and I ignored them as well.http://i.imgur.com/UtHuxPT.jpgAny idea what's going on here? Running this on a mac.That's actually really odd, because it appears that the font textures are screwed up. I'd like to know more about this one.I have a minor issue Mihara, but I'm not really sure how to go about solving it. It would be useful if I could know whether or not a plugin was installed.https://github.com/Mihara/RasterPropMonitor/issues/114Mihara : I think the problem with the Dev version of MJ are not related with the version number but with this COMMIT. core.target.Orbit was renamed in core.target.TargetOrbit to avoid confusion with core.target.orbit ( lower case o ). So it's most likely the origin of the problem.Er... That would mean that recompiling against a new build would not fix the problem and would be causing compile errors. That is not the case, or at least, was not the case last time I checked.I am willing to do literally whatever is best, but I want to be able to have people use dev builds of MechJeb and dev builds of my mod. If that means that we figure out this versioning nonsense, then fine. If that means I have to re-write the whole damn SCANsat plugin using some reflection or wrapper or some other mildly annoying (but performance retaining!), I will do that too.The very best thing to do would be for you to take over SCANsatRPM and embed it into SCANsat directly. Shims were only introduced because there was no other way in hell to deal with this, and I didn't want to break into the development cycle of someone else's plugins with my features. If you can match the SCANsatRPM background handler configuration, this module can load from the SCANsat assembly and will have native access to all SCANsat data, this will keep modules where modules belong. RPM API was designed so that while it's kind of limited, it's consistent, simple, and does not require hardlinking at all, nor does it care about version numbers, so that would be as future-proof as it gets.Failing that, though, I have no clue what to do, nor do I have a clue if the licenses for SCANsatRPM (which is GPLv3) and SCANsat itself, (which is BSDv2) can mesh in such a way. (though in as much as I wrote SCANsatRPM, I can definitely state I do not care.) Any chance we could see a plugin for RemoteTech?Not from me. Supporting even two interface DLLs has proved to be extremely cumbersome. RemoteTech can provide an RPM plugin as detailed in all the handlers documentation, it should be easy -- but I will definitely not be writing one. Mihara:Starting with the next SCANsat release (and the first by me instead of danny), I will be assigning the version numbers by hand. I assume your decision to omit version numbers from your assemblies is a conscious one. I also assume that it has the effect of assigning the version string "0.0.0.0" to the assembly. I also assume that these two are equivalent. When and if I get a buildbot going for the dev versions, I will be leaving the build information in some other field (description? name?) so that they will be loaded correctly.Waitwaitwait.I'm definitely not doing either of that. As far as I can tell, all my assemblies have a specific ProductVersion and FileVersion and what not. I definitely did not expect anyone would hardlink to RPM precisely because it's such a pain. I'm putting together a spaceplane cockpit and would really love a machmeter. A cursory search found this post from several months ago, saying it should be possible. So that sounds good.Is it still possible? Planned? Forgotten about, maybe?Possible, planned, forgotten about. I can take the requisite piece of code directly from FAR -- it's short enough -- but I'm unsure about licensing issues. I can also try to leech data off FAR, but that would require another dll shim, which are a real pain as described above. The very best thing would be for FAR to provide a variable handler: https://github.com/Mihara/RasterPropMonitor/wiki/Variable-handlersOh, and speaking of kerosene that you mentioned, https://github.com/Mihara/RasterPropMonitor/issues/115 Link to comment Share on other sites More sharing options...
Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 As far as I know the pages displayed are actually supposed to be fully customizable.I bet there is some info on that on wiki or just around the web...See the official RPM docs linked in the opening post. No, really.What is wrong with the docking cameras on the Goodspeed ports?Nothings is in front of the port that would obstruct my field of view but I can only see a wall or a surface of some sort in front of me all the time.On docking ports, the camera is looking out of the reference transform of the port. If the reference transform is obstructed because it's embedded in the body of the model, tough luck. You can use JSIExternalCameraSelector module, which provides a named camera that can be moved away from the point where it is obstructed.How can I integrate the docking cam from the Lazor pack into one of the pages?Is this the thing done in the ALCOR?No, this is not the thing done in ALCOR. ALCOR just has a very detailed RPM configuration, far more than the example default, that's all. Link to comment Share on other sites More sharing options...
Kitspace Posted June 9, 2014 Share Posted June 9, 2014 So, there is a page with more information added manually that makes me think that it is a lazor page in the ALCOR?Still, is that possible to implement that camera window into one of the cockpit display pages out there? Link to comment Share on other sites More sharing options...
Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 So, there is a page with more information added manually that makes me think that it is a lazor page in the ALCOR?Still, is that possible to implement that camera window into one of the cockpit display pages out there?If Romfarer wants to do it, it would be trivial for him to implement by using RPM's public API. He would not need to write more than a page of code which would, from here on, never change.If I wanted to sew RPM and Lazors together, it would create yet another shim dll that I have to maintain, and I have my hands full with two already, so I'm not planning to do that, sorry. Link to comment Share on other sites More sharing options...
Kitspace Posted June 9, 2014 Share Posted June 9, 2014 Where can I read something about doing it myself?Sorry, what is that camera module and how to get it?By, the way, I am from Moscow too and I do not quite get what is wrong with our country. Also, we could switch to russian anytime Link to comment Share on other sites More sharing options...
Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 Where can I read something about doing it myself?Sorry, what is that camera module and how to get it?I don't understand your question at all, actually. But if you want to read, start with the documentation:https://github.com/Mihara/RasterPropMonitor/wiki/Background-handlersYou just need to hack that interface into Lazors and you're done.By, the way, I am from Moscow too and I do not quite get what is wrong with our country.Roskomnadzor is not enough? Also, we could switch to russian anytime Forbidden by the rules of this forum. I got moderated for this in the past, but you can always send a PM. Link to comment Share on other sites More sharing options...
Schmonzo Posted June 9, 2014 Share Posted June 9, 2014 installed the mod on a fresh install and extracted it (via modmanager) into the gamedata directory, the hullcams show up but no monitors in the cockpits... help anyone? Link to comment Share on other sites More sharing options...
Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 installed the mod on a fresh install and extracted it (via modmanager) into the gamedata directory, the hullcams show up but no monitors in the cockpits... help anyone?If ModuleManager dll was not installed you won't get monitors in the cockpits. Blame your modmanager. Link to comment Share on other sites More sharing options...
Schmonzo Posted June 9, 2014 Share Posted June 9, 2014 If ModuleManager dll was not installed you won't get monitors in the cockpits. Blame your modmanager.I blame myself, had too many old module managers, so deleted them and meant to update, but forgot to put modulemanager back in.... SORRY FOR WASTING EVERYONES TIME!!!!Have a nice day! Link to comment Share on other sites More sharing options...
Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 Ok, for anyone that cares.For the next release, I'm considering the idea of splitting RPM into multiple packages, with an eye on handing off at least one of them to someone else. Like maybe Hyomoto. Anyone who cares to voice an opinion, please do so at https://github.com/Mihara/RasterPropMonitor/issues/124 Link to comment Share on other sites More sharing options...
erendrake Posted June 9, 2014 Share Posted June 9, 2014 @Mihara I am the current kOS maintainer. I would be interested in working with you on getting kOS working with RPM. Im not quite ready to start yet but after our next release i think it would be a fun project!We currently have two windows, the terminal and a code editor that is invoked with a terminal command. If you would like to help us out let us know. Link to comment Share on other sites More sharing options...
Mihara Posted June 9, 2014 Author Share Posted June 9, 2014 (edited) We currently have two windows, the terminal and a code editor that is invoked with a terminal command. If you would like to help us out let us know.As long as you kept the logic of the original kOS, which had a simple character buffer, a PageHandler which defines a key for every key kOS handles and passes them to kOS, while replying with the screen buffer for every page request should be trivial. I very nearly started on that myself, but back then the future of kOS was kind of unclear and I didn't want to make another interface shim. Now I want one even less. Feel free to PM me with any questions, but basically, https://github.com/Mihara/RasterPropMonitor/wiki/Page-handlers should be almost all of what you need to know.P.S. Oh, and ALCOR has a monitor model designed specifically with that in mind which you can use for testing. Edited June 9, 2014 by Mihara Link to comment Share on other sites More sharing options...
MrOnak Posted June 9, 2014 Share Posted June 9, 2014 @Mihara I am the current kOS maintainer. I would be interested in working with you on getting kOS working with RPM. [snip][MrOnak sniggers in the background] Link to comment Share on other sites More sharing options...
erendrake Posted June 9, 2014 Share Posted June 9, 2014 [MrOnak sniggers in the background]Keep talking Onak, ill rope you into the project and get you to implement it Link to comment Share on other sites More sharing options...
MrOnak Posted June 9, 2014 Share Posted June 9, 2014 Argh no please, not one more language to write stuff in Link to comment Share on other sites More sharing options...
tygoo7 Posted June 9, 2014 Share Posted June 9, 2014 (edited) Does anyone know why the monitors aren't working and they are grey normal maps that I can't click on? I'm using ActiveTextureManagement Basic with Green Skull's configs and Hyomoto's monitors.EDIT: Anyone? Edited June 10, 2014 by tygoo7 Link to comment Share on other sites More sharing options...
Mihara Posted June 10, 2014 Author Share Posted June 10, 2014 Does anyone know why the monitors aren't working and they are grey normal maps that I can't click on? I'm using ActiveTextureManagement Basic with Green Skull's configs and Hyomoto's monitors.EDIT: Anyone?I know that this happens when the plugin failed to load so hard that it can't even tell you why exactly. (Which it usually does, loudly, when it didn't fail that hard.)I also know that in every case that I have investigated so far, it turned out to be an installation error, which is why I usually stay quiet, since to tell you where it is exactly requires puzzling through megabytes worth of KSP_Data/output_log.txt and there's only so many times I can do that before it gets old. Link to comment Share on other sites More sharing options...
K3-Chris Posted June 10, 2014 Share Posted June 10, 2014 Is there any canada arm:ish solution that works with RPM btw? Would be really cool to be able to manipulate your cargo in a shuttle/SSTOSP from the IVA. Link to comment Share on other sites More sharing options...
Mihara Posted June 10, 2014 Author Share Posted June 10, 2014 Is there any canada arm:ish solution that works with RPM btw? Would be really cool to be able to manipulate your cargo in a shuttle/SSTOSP from the IVA.Not yet. But sirkut asked me for advice on making an RPM page handler in IR, so eventually there will be. Link to comment Share on other sites More sharing options...
K3-Chris Posted June 10, 2014 Share Posted June 10, 2014 Hmm IR is nice and all but not ideal for canada arms, I wonder if the romfarer/lazor one could get patched into a RPM view... Link to comment Share on other sites More sharing options...
Mihara Posted June 10, 2014 Author Share Posted June 10, 2014 Hmm IR is nice and all but not ideal for canada arms, I wonder if the romfarer/lazor one could get patched into a RPM view...I'm very definitely not doing any new interface shims in the foreseeable future, so you'll have to ask Romfarer to support RPM if you want that to happen. Link to comment Share on other sites More sharing options...
K3-Chris Posted June 10, 2014 Share Posted June 10, 2014 Yeah obviously not asking you to do it, and I'm guessing Romfarer is busy with other things, if I wasn't a talentless hack I could give it a go. Link to comment Share on other sites More sharing options...
Mihara Posted June 10, 2014 Author Share Posted June 10, 2014 Yeah obviously not asking you to do it, and I'm guessing Romfarer is busy with other things, if I wasn't a talentless hack I could give it a go.Well, that is always an option. You don't even need to fork Romfarer's plugin, (I think his license doesn't allow that anyway) you can just hard link to it and present an RPM handler interface on the other end.But, you'll have to support it later and change it whenever Lazors changes, which is what's stopping me. Link to comment Share on other sites More sharing options...
K3-Chris Posted June 10, 2014 Share Posted June 10, 2014 Yeah, I got experience in that department, mod inter-connectivity isn't a simple affair. Link to comment Share on other sites More sharing options...
Brucey Posted June 10, 2014 Share Posted June 10, 2014 Mihara. If you get some time, please take a look at post #1333 on this thread and the follow up discussion. It seems the data for delta angles and distances are not displaying the correct values in the docking camera. I've tried with all the different versions of RPM and also tested it with the lazer docking cam addon installed for comparison. (Lazer docking cam works correctly) Probably not an issue for most people since they just use autopilots but I thought I would mention. (Just FYI) Link to comment Share on other sites More sharing options...
Recommended Posts