PeteTimesSix

I actually coded those display modes back when stock aerodynamics were less-than-stellar, like three versions ago. I dont even remember what it hooks into for stock and the FAR integration is probably majorly out of date by now (not the mention the complete lack of NEAR integration). I might get around to updating it? Right now it turns out Im actually going to be quite busy for a while due to a sudden onset of deadlineitis. I think there was something... right. If you open up the .cfg file for the monitor youd like to change the default value for(for example, for the basic MFDs that RPM puts into stock capsules, thatd be <installPath>\Kerbal Space Program\GameData\JSI\RPMPodPatches\BasicMFD\MFD40x20.cfg) and find the page entry for Vessel Viewer: Then you can simply drop in latencyMode = 0 (for OFF) anywhere, like so: And it will be the default for that particular monitor prop from then on. You can find the other configurable options here, though Im not ENTIRELY sure how up-to-date that page is. (though I should point out the latency flicker thing has since been fixed on both my and MoarDV's end)

I only uploaded the complete version to KerbalStuff (didnt want to put up duplicate mod listings) so thatll be the only version currently up-to-date on CKan (assuming its automated). I might have to look into cleaning that up as well but honestly I have no idea how to CKan. Can you check the console for any null pointer exceptions or any other errory-looking printouts? EDIT: Nevermind, just checked the RPM thread. MOARdV apparently introduced a screen clear every frame to deal with some-bug-or-other, and since the latency modes rely on keeping renders from previous frames, they get wiped on every frame theyre not redrawn on. Seems its being looked into? Just switch latency mode to off for now, I guess.

Well, I dont know what it was that caused the problem, but recompiling with the newest API version seems to have fixed it...? Ive also fixed that longstanding wireframe bug while at it. EDIT: Ive also put it on KerbalStuff, like all the cool kids are doing it these days.

I'll look into it.

And done. If it fails horribly Id like to know about it, as usual.

I looked at it. It, um, worked fine, I just had to click through the wing first (because the parts were attached to it, not the pod). Im not sure if that means there's something else wrong or if you just didnt think of doing that? That being said, I did still poke at the code - not the least because as it turns out I never did implement scrolling, so its entirely possible to attach so many parts to one part (like, say, a dozen solar panels) that anything you might want to actually interact with is listed off-screen... so thats a thing I worked on. I also plan to make parts that are part of a symmetry group only be listed once, and possibly finally put in a action list-based part selector.

Well its not ideal. You could probably strip it to just a capsule + whatever it is your science modules are attached to and anything directly attached to that for the same result? If the remaining parts belong to like two or three mods I could just install those and it'd be fine.

I make no promises, but I might find some time to take a look into the issue (I've been avoiding KSP till 1.0 comes out). It might be helpful if you could pass me a .craft file that demonstrates the issue.

Funny you should mention that...

So the programming bug bit me again. So I made this. And reworked the special modes subscreen so that it looks like this: Why is this the least bit interesting? Well, because of this: That's right, adding new custom display modes is now as easy as dropping another .dll in. Now this makes it a lot easier to add things for me, but more importantly, it makes it possible for YOU. Now, I'm not sure how many people actually use this mod, but I do know that its a nonzero positive number, so there ought to be someone interested in taking a poke. Ive set it up to be reasonably easy, just take a look at the source for the example DISCO MODE plugin. I plan to add futher functionality down the line (such as overlaying icons, lines or other primitives) if there's interest. See first post for links.

Apparently there's been a change in addon posting rules? How devious! Luckily I happened to randomly check the forums (despite not having played this game in months), so that should be fixed. I mean, I dont actually know. Licenses are confusing. Anyway, while at it I replaced the included moduleManager with the latest version, so if it stops working I'd like to know.

...both of those are already a thing? Its located under Info in stock RPM.

Argh. I thought I fixed that. Can I have the save? EDIT: OK, I THINK I fixed the Alcor issue, give it a shot. The staging diagram thing Ill need the .craft file to fix properly but I did put in something that should hopefully stop the whole thing from falling down at least.

*shake shake* The magic 8-ball says... yes! (check first post)

Also fair. Ive written down what I remember changing.

Fair 'nuff.

One I keep running into - turns out KSP never bothers turning wireframe mode off when rendering. Not suprising really, but it means that if theres a crash anywhere in my rendering code it stays on. Anyway, new version! Because at this point Ive done everything Ive originally set out to do, I figure Vessel Viewer deserves a move into the releases section: http://forum.kerbalspaceprogram.com/threads/80581-0-23-5-Vessel-Viewer?p=1168414#post1168414 ...and with that, I bid this thread adieu.

Introducing (again) Vessel Viewer! Ever fly an IVA mission, happened to hear an explosion and wished you knew if it was antenna no. 54 or your main engine that just blew up? Like to fly without the GUI but also a fan of knowing how much fuel there is in your tanks? Wondering just how hot is Deadly Reentry making those wings? Perhaps you'd like a more visual way of telling whenever your wings are stalling when running Ferram Aerospace? Ever wished you could activate engines and take science reports without having to go into external view, but too lazy or forgetful to setup action groups? I've got you covered. Complete edition download (requires Toolbar, RasterPropMonitor) The same on KerbalStuff Standalone download (requires Toolbar) RPM download (requires RasterPropMonitor) Comes with a User manual! Source code. License. Current list of extensions: DISCO MODE example plugin (included) Part Selector (included) I would LOVE to add some more to the list. Throw 'em at me, people!

This question has come up before. It would certainly be possible, but the thing is - anything I could throw together would pale in comparison to the excellent piece of work that is TAC fuel balancer, so I dont really see the point. I might look into integrating with it at some point down the line, but not any time in the nearby future.

This might be of interest to you.

Well, I make no promises, but I DID just finish burning the DVD's to go with my bachelors thesis and thus might actually have some of that mysterious substance known as "free time" my dusty, age old diares speak of sometime soon. Possibly. Maybe.

Its not like I can take any credit, unit327 figured it out and besides its just moving one line down one by one line... ...eh, screw it, I need the ego boost right now. KOS? The autopilot mod? Im not sure what it has to do with Vessel view, honestly. Its certainly possible, though Im averse to hardcoding like that. ...I could probably just list out all the modules with activable actions avaiable on the parts on the ship and sort by those, put in some manual filtering. Ill keep it in mind if I find some time to actually work on this.

...huh. Well okay then. Made the change.

There would be, if I didnt mysteriously forget to add that one specific option to the configurable settings. Oh well, its a quick enough fix. Right. Updated the RPM version, just add: to any screen you'd like to default to latency off. For the standalone itll take slightly more work (I need to actually have config files for it first), so Ill add it to the Nebulous List of Things to Do in The Future.

It shows the parts directly attached to the selected part (root by default). To get to, say, the engine on the bottom, you have to travel down the line of fuel tanks, so to speak. Id love to fix that, but honestly I have no idea what the issue could even be. I dont have linux installed on anything at the moment and besides Ill be busy for quite a bit (HIGHLY underestimated how much work Id need to get my bachelors project done) so dont hold your breath :c