Jebs_SY

I have tried it with 0.2.3, 0.2.2, 0.2.1, 0.2.0... but 0.1.8 was the "first" where the right click was working. Log follows.

@linuxgurugamer I have found a (small?) issue, I think. When having JC 0.2.0+ installed, the right click button for mod settings does not work. For example the Automated Science Sampler and the Kerbokatz Small Utilities PhysicalTimeRatioViewer. Both in the flight scene. When having these both Kerbokatz-Mods installed, they can be grouped in the Kerbokatz-Toolbar. However, right click on the button gets one to the settings, which is not working for me. With JC 0.1.8 it is working. I think I may stay with 0.1.8 for now, cause the mod filter is just priceless. BTW, could the JC toolbar functionality be toggled on/off by a setting, easily?

Family and christmas first, thats for sure. I would say.

I can confirm this. After using camera tools the camera focus goes to the root part, not the center of mass. When right clicking the root part, it also says "Reset Camera" and not "Aim Camera" so the focus is indeed "officially" on the root part. Would be nice if we can change that back to Center of Mass = No part focussed.

@linuxgurugamer I am happy to say that everything is fixed on my installation after a quick test. I can move chatterer button to the JC-Toolbar, it works and the blank line from the mod list is gone, also. Great work. As always. o/

@linuxgurugamer I would have a feature suggestion. Could the mod-filter-window get some preset buttons? Maybe 1,2,3,4,5. With the possibility to save a mod selection to that button. Save could be something simple CTRL + Button1, maybe. And Button1 just restores the selected mods. For what it would be useful? I have plenty part mods, for example 10, but regarding the loading times I consider, that maybe 1,2,3 out of the part mods could get removed later. However, when loading the savegame then, the ships with those parts get deleted. Cause of that I build mission dependent. For a short mission, I use parts from all mods. For a long and maybe important mission, for example a scansat or a ISRU on a far planet, I only use the stock parts and parts from mods that stay100% in my installation. With such preset button row one could easily switch between some mission / part profile list. I almost would say these buttons could even be more/faster accessible then in the part filter menu, but if they are there that would be fine enough. Just the case "new mod adds new parts" must be considered, but when not in the "not selected" list then just show it. So maybe the saved preset should save the deselected mods. Just as an idea. Don't know if it's possibe / how much work it is.

@linuxgurugamer OK, I had just run a test with 0.20 again. Seems to work fine with USI-Servo, Deep-Freeze and KSP-Interstellar UNTIL I move Chatterer into the JC-toolbar. Then it's broken. There was something with chatterer. Chatterer had a blizzy-toolbar-icon, then there was some kind of library cleanup (was it linq?) and chatterer only had stock toolbar support. But the author said, that he wanted to support blizzy again as soon the (linq?) cleanup is complete.

Hello, I was not using the hide function but the move to a janitor-folder function. IIRC I moved the same buttons. Chatterer, USI-Servo and I think also the Deep-Freeze and KSP-Interstellar buttons. The servo controller should come with USI Contruction. I am not sure about the following information: I think it was working one time with JC version 0.20 in that game-instance, I had moved the buttons to the JC-Toolbar. I think after restarting KSP it was then not working anymore, but it can be, that the next restart was already with 0.21. I have to try again, but don't have that much time atm. So read this information as "not sure".

Same for me, but instead MJ in my case the blizzy toolbar and KER layer is getting switched on and off.

Hey @Morse you could save my template into a PreciseManeuver.version file and put it on github to (for example) => https://raw.githubusercontent.com/radistmorse/KSPPreciseManeuver/master/GameData/PreciseManeuver/PreciseManeuver.version and at the same time you include the file in your download zip as PreciseManeuver.version in the PreciseManeuver folder where also the dll's are. Now 2 benefits; When you release a new PM version, you just bump the VERSION field in the github PreciseManeuver.version file and in new release zip PreciseManeuver.version file. When a user is using AVC (which is highly likely (and as mod author you even could include avc-mini in your release see here)) then AVC compares the local installed version file and recognizes, that the github file version is higher and the user gets a notification, that a new version is aviable and a download button to your repro is shown, the user directly click on it. The second thing is, the CKAN system automatically indexes the version file included in the release download. (If they set it up that way, which I would ask for, then). So your mod is automatically indexed, listed and installable via CKAN. The only thing needed is keeping the mod-version and the ksp-version/min/max fields in the version files up 2 date. Nothing more. Just if you are interested. If not, no problem, too. See also: http://ksp.cybutek.net/miniavc/Documents/README.htm

@linuxgurugamer Can it be, that issues are still disabled for the fork? I can't find it. I'm sorry. I made a video, cause it's hard to explain. BTW, regarding the feedback here, I assume that I am one of the few / the only person that uses it, so it should have absolutely no priority. I almost didn't wanted to ask... https://www.youtube.com/watch?v=D6jW17Eqk0c PS: This is the same problem, the old image viewer got with the KSP 1.2 update. I was hoping, that recompiling it for 1.2 would fix it.

@linuxgurugamer Does this explain?

This is GREAT! PS: In the mod list (of my highly modded install) I have a green switch with no label over Asteroid Day. I don't know if it's a beta thing or I have a mod without name installed.

@linuxgurugamer If you find some free time, could you maybe take a look at a small issue with the keys? When using imageviewer with the mouse only, it works fine. But for that, one has to click "hide image window" to close the image window. However, when closing the image window with ALT+i, then it comes back on screen unwanted after a scene change. And when opening/closing the image list with CTRL-i then I regulary end up with 2 or 3 image lists. So the key combinations are not working perfect, yet. If you can't reproduce it, I can make a short video. Maybe/hopefully it's easy to find/solve. It's not that important, just if you maybe find some spare time. o/ Maybe one could use left click on the toolbar icon to show the last selected image and right click for the menu?

Is there a way to put it back into blizzys toolbar, yet?

Is it possible to remove the realchute icon from the flight screen? Or at least put it into blizzys toolbar, maybe?

Hey @linuxgurugamer I get a ModuleWheel related error with the Rover Contracts on KSP1.2.2. Changing ModuleWheel to ModuleWheelMotor in iteratorRover.cfg fixes it, however I am not sure if thats the intended solution. But I assume.

Hey @Morse, If you find a little time, would you consider adding a PreciseManeuver.version file in github and the download archive? I've attached a template that should be (almost complete) (only check the github path). With the .version file users get a download notice, when your github-version is newer than the installed version, if they use AVC. Same time CKAN analyzes the .version file included in the release download and so precise maneuver will be autimatically indexed and versioned in the CKAN, which would be nice. Note: -KSP_VERSION is mandatory, KSP_VERSION_MIN and KSP_VERSION_MAX is optional. -Github Reference is optional -VERSION file specs. o/

@sarbian If you find a little time, could you maybe push ksp_version_max in the .version file in the download to 1.2.2 or 1.2.99, that CKAN recognizes the compatibility?

@Crzyrndm So, did 3 hours of testing and found out: -KSP 1.2.2 + KSP-Interstellar Extended 1.11.10 + Filter Extensions 2.8.0.2 and you get the errors that I've posted 1 post above when entering the VAB. -removing F.E. OR KSP-I and the error is gone -KSP-I seems to use a user category -Each time the game is started with both mods, the KSP-I user category is added once more. So 5 starts => 5 times of the KSP-I categories in the editor. --Same for the SpaceY user category, they get added once per game start, too. But: Removing F.E. completely and then starting KSP and remove a item from the KSP-I user category by clicking the small X, gives an (similar?) error as well: So I think I am here at the end of what I can do. Don't know if its a F.E. thing or a KSP-I thing or something of both.

@Crzyrndm Just a update to my reported errors with 2.8.0.2... they disappear when removing the warpplugin/Interstellar folder. So maybe it's some parts from Interstellar. Maybe it helps reproducing. However, I assume you test with these / some big mods anyway?!

@Crzyrndm Categories are there now, I think. Thx for your effort. But at least I still get some log errors. (Highy modded install):

@Padishar I just debug my 100-mod 1.2.2 setup, cause allocation rates around 30-40MB/s are not nice... and I wonder, would it be possible/useful for memgraph to show/calculate the average allocation rate between the 2nd last and last garbage collection? Maybe only when the memgraph-GUI is shown on screen. Do you think this is useful? EDIT: Another interesting thing to compare different setups would be the interval. However, interval alone doesn't help, cause the heap can be different big. So maybe Heap-Delta (Max-Min) would be useful, too. Or maybe even Interval / Heap-Delta. This should result in a comparable performance number, or?

@Padishar Could you maybe update the version file in the github release download, that CKAN lists it correct again? ATM there's two times ksp_version_min inside. I assume you wanted ksp_version=1.2.2 and ksp_version_min=1.2.0?

@MOARdV If I see this correct in the distant object netkan file, it is pulled out of the version file in your release download. You have ksp_version=1.2.0 and ksp_version_min=1.2.0, so for CKAN it's 1.2.0 only. It would work with ksp_version_min=1.2.0 and ksp_version=1.2.2, which requires a version file update each new KSP version. Alternatively add a ksp_version_max=1.2.99. However, that's just by my observations, but I think it should be correct.