dmmarkow

Hello First let me say thank you Ezrlilc for Hyperedit - it has been invaluable for playing and testing designs - could not imagine trying to tackle Eve without it Have noticed what appears to be a bug and it affects how Remote Tech works, but appears to be there even with KSP-1.04 vanilla (using Linux 64bit) When I use the orbit editor, do a simple jump to Eve on a rocket (Mk1 capsule and a solid rocket motor only), add a maneuver node, the Delta-v required will gradually increase over time. Strangely, if you go back to space center and then select the vessel to fly again, this delta-v creep does not occur. The creep only occurs during the initial jump. What is even weirder, the creep only seems to occur on the initial jump from the space center. If one jumps to Eve orbit, then Kerbin orbit then back to Eve orbit, no creep. I have tested this with KSP-1.04 with no other mods than Hyper-Edit. When Remote Tech is added, the delta-v creep confuses the flight computer making it so the engine does not turn off as the end of burn is not properly identified. Understand earlier in the thread there was a problem with MechJeb, maybe this is related as the Remote Tech flight computer leverages the MechJeb calculations. Again, great mod, jumping back to the space center or a save fixes the problem so is easily manageable Thank you VR dmmarkow

Starwaster Thanks - the stutter does act up unpredictably and is annoying (and doesnt happen under 2.5.8). I have tried dissecting the Player.log - found it hard and non-standard based on load - hard to make a consistent diff. I have a lot of mods installed (Umbra Space Industry series, TacLife and remote tech) - appears these load in different sequences making comparison hard. Size is also slightly different in each load. Its almost a meg in size - dont want to spam this thread, should I be looking for some error or an option to prune the chaff in the log? Willing to email 2.5.8 and 2.5.9.... Thanks

Hello, just to add to the strangeness, after having used 2.5.9 and severe lag started, went to the setting page off of the main menu and speed went back to normal - didnt even have to hit a button, just cancel....very strange - must be an interaction with the nvidia driver, the KDE desktop and KSP that somehow vsync is triggering....

Hi First want to thank Sarbian and the team for making such a great utility Not sure of the problem, but just upgraded to 2.5.9 as part of USI Kolonization Systems v0.22.6 and system slowed incredibly after the load screen. I have a 64bit linux system (slackware 14.1 with latest patches, ge260 nvidia graphics card using the latest nvidia drivers). System does not seem to respond well to the reset of the vsync rate (if that is the only change from 2.5.8 to 2.5.9) Replaced 2.5.9 with 2.5.8 and went back to original speed, no slow down - just wondering if the change is a linux vs windows issue - certainly want the linux version to be compatible to future changes Thanks again