Framerate
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by Framerate
-
-
framerate: The "first" flyby, or the repeatable crewed lunar?
Although the title does not state "first", I assume this is an one off contract based on the big reputation gain.
-
Frameratae: We don't touch how rep works, or how strategies work...
Thanks for your reply Nathan!
I think the problem lies with that specific contract (crewed moon flyby) because when doing the crewed moon orbit yesterday my rep gain was positive.
On a different note, remember my probes orbiting and landed on the moon, that magically warped to Saturn's moon Iapetus last big update?
Well I save edited them back to earth's moon, and continued on. This last big update got them warping again. This time to Jupiter's moon Io, and since Io's diameter is bigger, my orbiting probe crashed :'(
Edit: If anybody finds themselves in the same situation the fix is to change REF = 8 to REF = 10 for the relevant vessel in the save file persistent.sfs
-
Well you should be getting negative reputation for that mission. Your administration policies are taking away too much reputation. Can they be set for over 100% reputation loss in the administrative building?
I'm pretty sure you got that backwards. Reputation in green is supposed to be the gain after deductions from policies, not the original value.
I'm running the 60% policy, and have done that since my 2nd launch, and it's been working well until this recent update.
-
Just want to report that I'm getting negative reputation since the last update.
My math seems to show that i'm getting the value in the parentheses instead of the value in green for contracts as shown bellow.
-
RF v10.6.1 *should* fix the issue. Let me know if it doesn't!
Woha! That totally fixed it! :-D
Talk about on the fly bugfix!
Thanks Nathan!
-
could that be part of test flight? because that is not uncommon malfuction in rocket engine clusters, or having some burn out early I seem to remember a satern test lauch had the 2nd stange hand an engine burn out early, so the buth when the gidince package tried to cut the fuel flow, it cut it to a deffren engine so it shut down early to
Your logic is sound, but I don't have testflight installed :-)
Framerate: I've heard similar scattered reports of engine clusters having some of their number fail to ignite. Scott Manley hit that for example. I'm wondering if it's something to do with the stock resource request system, since my code looks ok. I'll be digging into it...Thanks Nathan! Please let me know if I can be of any assistance!
-
I'm having problems with the LR87-LH2 engine.
First only 2 of 3 engines in a 3 engine first stage cluster would ignite.
The error message read in the lines of: "Insufficient resources to ignite"
This was very consistent.
After fiddling around I abandoned that on the basis that it was a vacuum engine despite of the very nice ASL ISP
So swapped the three LR87 in favor of a couple of LR79s. Weird thing was that the problem continued and only 1 of the 2 engines would ignite on launch.
Interestingly I had a LR87 powering the second stage a swell. Swapping out this engine fixed the problem.
So it seems using the LR87 anywhere on a rocket induces ignition problems for all engines.
All mods are up to date, is this reproducible or a bad install?
-
Just encountered a wierd bug after updating to RO 10.3:
In my RP Zero saved game I had one probe in orbit around the moon and one landed on the moon north pole.
When I continued the save today after updating all mods using Ckan, my probes where no longer at earths moon, but at Saturns moon Iapetus, and all of a sudden I got a whole lot of Iapetus contracts.
Is lesson learned here not to update mods during a playthrough?
Did some more investigation into this and found out that Earths moon has changed its ID from REF = 10 to REF = 8
Easy enough to change in persistent.sfs, but this does not change the fact that Im still getting Iapetus contracts!
Anybody know how to fix this?
-
Just encountered a wierd bug after updating to RO 10.3:
In my RP Zero saved game I had one probe in orbit around the moon and one landed on the moon north pole.
When I continued the save today after updating all mods using Ckan, my probes where no longer at earths moon, but at Saturns moon Iapetus, and all of a sudden I got a whole lot of Iapetus contracts.
Is lesson learned here not to update mods during a playthrough?
-
Don't know if this has been brought up before, or maybe its working as intended, but I just returned after doing these three significant prestige contracts using a single probe just to have them reappear again in the Mission Control:
Oh and upgrading the administration building as early as possible and getting the 60% Fundraising Campaign is way overpowered effectively doubling the reward from significant prestige contracts.
My space program is already filthy rich, and now ill be able to do these three contracts once more granting me another $720.000 spending just $5.600 on the probe.
Granted I'm playing on normal, but still.
And did I mention that Ill able to do this at least twice?!
Another thing: mechjeb ascent guidance will still be available regardless of the guidance rating, giving you the possibility to use this to orbit, and then have a small core to control the last stage(s)
Is this working as intended as well?
Seems a little cheaty, but then again so does mechjeb :-P
[1.2.2] Realistic Progression Zero (RP-0) - Lightweight RealismOverhaul career v0.53 June 12
in KSP1 Mod Releases
Posted · Edited by Framerate
That video was really old school but informative! :-D