Nudles

The link for the 1:58 time mentioned above.

I got the data using the benchmark in the free version of FRAPS, and the files it created in Microsoft Excel to create the graphs.

Hey AndreyATGB, you misunderstand the situation. You can get 300 fps and still have a low a frame rate. For example, I am getting for example 144 fps (on my 144mhz monitor), but it is far from smooth. Because during that one second,I get lets say 143 frames for the first 3/4 of a second, then the last quarter of a second I get 1 frame. So technically that is 144 FPS... but it is veeery jerky . So whether I set the framerate to 30, 60 or 120, it is still jerky. Because the frames are not evenly spread throughout the second its not true high fps. So in a sense its 144 FPS for a few seconds, and then 4 FPS, and it keeps alternating this pattern. But when looking at the graph it gives a false picture, without context.

Now I am noticing it when the Delta V window is not open, although not as pronounced or as frequent. Is it possible to turn it off completely when not in use? And I don't mean for you to go to the trouble of coding that, I mean is there something I can do on my end to stop it making checks whilst the window is not open? Other than not attaching it, of course! Such as an option in a config file, to tell it to do fewer or no checks when no windows are open. If you're like me, you like graphs. This is it without the frame limiter on.

Hi sarbian, thanks for the reply , and thanks for MechJeb. MechJeb does so so much that there really is nothing to complain about from me! Great job on it. So if this cannot be addressed, it's really not an issue. Also, my apologies as I did not mention it was version [0.23.5] MechJeb 2.2.1 .

Hi pheonix_ca the fraps suggestion worked perfectly, chart below. For the first 30 seconds I sat the camera stationary, fewing the rocket in the hanger, holding the mechjeb gadget on my cursor over the rocket. At the 31 second mark, I clicked to attach the object, starting MechJebs delta v calculator and watch again, with the camera stationary. The mean frame rate per second without mechjeb was 170, and with mechjeb running it was 135 and the 'spikes/jittering' started to occur. Each dip/spike gives the average fps (please excuse the redundant part of the y axis title , where i say "FSP Per Second"...) when playing. In the background I can see the vehicles "jumping" very slightly every few seconds. When I ran the conditions in reverse, I got practically the same results, 140 FSP with MechJeb and 180 FSP without. So on average MechJeb is reducing the frames by 40 FSP. If it is possible to dedicate a single core to MechJeb I would do that, as I think the jittering might be caused by MechJeb hogging the CPU every few seconds. Original post, for context for others reading.

Some good ideas there, thanks. I'll look into trying these when I get home. Just as a reference, the most noticeable 'jerk' is at about 8 seconds. Btw, nice guide on geostationary orbit, I'll be trying that later too.

I think this is the right place to post this. I don't know if this is a MechJeb, game or other bug, or what. Low frame rate youtube vid: http://youtu.be/sUOPhwqmR2M Higher frame rate but lower bitrate version: http://tinypic.com/r/jgs1w9/8 As the video somewhat shows, the camera is jittery when running the delta v window in MechJeb, the framerate is fine though (on my screen). It does not go like this when the other MechJeb windows are open, just the delta V window. This happens inside, and outside when 'flying'. It's much harder to tell in youtube videos, because it makes everything jittery. The jittering I am talking about are the sudden jumps every few seconds. On my screen, it is silky smooth, except at those points. My guess is that MechJeb Delta V calculator is recalibrating its stats every few seconds, causing it to do this. Anyone got a suggestion on how to fix this? Other mods installed: Kerbal Alarm Clock, Enhanced Nav Ball Computer specs are: i5 3570k, AMD HD 7950, SSD and 8gb ram.

edit: Double post