-
Posts
108 -
Joined
-
Last visited
Reputation
5 NeutralProfile Information
-
About me
Spacecraft Engineer
-
[1.1] AFBW v1.7-beta (Joystick & controller mod)
The Pink Ranger replied to nlight's topic in KSP1 Mod Releases
Exact same problem here. Running Winblows 8.1. -
[1.0.4]Better Buoyancy v1.4 - obsolete as of 1.0.5; 7/29/15
The Pink Ranger replied to ferram4's topic in KSP1 Mod Releases
Yah. If he isn't behind this upcoming aero update then there's something wrong with their hiring process -
[1.0.4]Better Buoyancy v1.4 - obsolete as of 1.0.5; 7/29/15
The Pink Ranger replied to ferram4's topic in KSP1 Mod Releases
+1 for CKAN -
Having a similar problem. If I write this: @PART [*]:Final { @RESOURCE [*] { @amount *= 5 @maxAmount *= 5 } } It only seems to affect the first resource in each part. However if I punch in each resource individually like this: @PART [*]:Final { @RESOURCE[LiquidFuel] { @amount *= 5 @maxAmount *= 5 } @RESOURCE[Oxidizer] { @amount *= 5 @maxAmount *= 5 } @RESOURCE[SolidFuel] { @amount *= 5 @maxAmount *= 5 } ... etc ... etc ... etc ... } Then it works fine.
-
LOL! Wow! I wish module manager had a way to check syntax hahahaha! Hopefully that works Anyway I'm not familiar with dimonnomid's work but I think it might be fairly simple to write a short patch that allows almost any parts mod to work with RSS/10x Kerbol. What I'm thinking is as follows: 1.) As per your calculations simply divide the mass of all parts containing engine and engineFX modules by about 6 2.) Also as per your calculations divide the masses of all parts not containing said engine modules by about 4 3.) As per TChapman500's calculations divide all stock resource densities by about 5 in order to bring them acceptably close to real equivalents (if other mods balance their resources around stock values then I'm thinking this blanket patch will bring them in line with the scale of RSS with minimal issues.) 4.) Not sure if this last one is necessary but no harm in testing it out: Multiply all stock tank volumes by about 5 ------------ The other thing I'm currently trying is this: Stock KSP balances around smaller scale planets by increasing everything's density. I'd like to see what happens when I tone the density of all parts down to realistic values and then balance them for the smaller scale planets by reducing thrust instead of increasing mass. I have a feeling that a lot of the strange behavior in KSP can be chalked up to everything having insane amounts of inertia. So basically all I'm doing is implementing all of the pseudo realistic changes above and then dividing thrust for all engines by the same factor I divided their mass by. Then I'll further tweak by relating the TWR of a certain size of rocket to its dV. So far I've got all of this done except the resource multiplier.
-
Okay so if I just adjust the resource densities to real world figures (as I've already done) then that should be enough to bring the stored energy somewhat in line with real world figures? The only reason the *5 multiplier is necessary for converting stock tanks to real fuels is because real fuels pretty much just changes the units right? Density part of the patch: // Squad Resource Definition Densities @RESOURCE_DEFINITION[LiquidFuel] // assume kerosene { @density = 0.000915 } @RESOURCE_DEFINITION[Oxidizer] // assume liquid oxygen { @density = 0.001141 } @RESOURCE_DEFINITION[SolidFuel] { @density = 0.00175 } @RESOURCE_DEFINITION[MonoPropellant] // assume hydrazine { @density = 0.001021 } //@RESOURCE_DEFINITION[XenonGas] //{ //@density = ??? //} Anyway even if my original intent doesn't make sense conceptually what can I do to get the resource changes to work (for future reference)? I tried splitting them up as follows and despite that module manager reports no errors on load it still doesn't work. @PART [*]:HAS[@RESOURCE[LiquidFuel]]:Final { @RESOURCE[LiquidFuel] { @amount *= 5 @maxAmount *= 5 } } @PART [*]:HAS[@RESOURCE[Oxidizer]]:Final { @RESOURCE[Oxidizer] { @amount *= 5 @maxAmount *= 5 } } ...... and so on and so forth for the others
-
Hey fellas. I'm trying to make a universal patch to make everything compatible with RSS without using MFT or Real Fuels. Trying to multiply LiquidFuel and Oxidizer amounts and maxamounts by 5 and this is what I have copy and pasted from my cfg file: @PART [*]:HAS[@RESOURCE[LiquidFuel|Oxidizer|SolidFuel|Monopropellant|XenonGas]] { @RESOURCE[LiquidFuel] { @amount *= 5 @maxAmount *= 5 } @RESOURCE[Oxidizer] { @amount *= 5 @maxAmount *= 5 } // What multipliers to use for the following? @RESOURCE[SolidFuel] { @amount *= 1 @maxAmount *= 1 } @RESOURCE[MonoPropellant] { @amount *= 1 @maxAmount *= 1 } @RESOURCE[XenonGas] { @amount *= 1 @maxAmount *= 1 } } Doesn't work. Can anyone tell me what I'm doing wrong here? Thanks. Edit: Caught the missing bracket. Still doesn't work.
-
[Stopped] 6.4x Kerbol System v2.0.1 - RSS Config [11/16/14]
The Pink Ranger replied to Raptor831's topic in KSP1 Mod Releases
Any chance you'll put this on CKAN? -
[1.1] AFBW v1.7-beta (Joystick & controller mod)
The Pink Ranger replied to nlight's topic in KSP1 Mod Releases
Seems to be working alright. I installed manually and didn't extract the relevant files to KSP's root folder. Thanks for the help. -
[1.1] AFBW v1.7-beta (Joystick & controller mod)
The Pink Ranger replied to nlight's topic in KSP1 Mod Releases
Alrighty here you go: output_log.txt Thanks! -
[1.1] AFBW v1.7-beta (Joystick & controller mod)
The Pink Ranger replied to nlight's topic in KSP1 Mod Releases
Anyone else having issues seeing the main config screen? When I click the controller icon all i get is this: -
Hey can someone tell me what data mechjeb uses to launch into the plane of a target? I'm trying to make a custom window so that I can do it manually but I'm not sure what data I should be looking at. Should be the target's longitude of the ascending node right? I'm looking at this diagram and I'm guessing that the "Target LAN" field uses the direction from the center of the body you're on to your position over that body as the reference direction? I'm guessing I need to launch when "Target LAN" says either 0 or 180. Am I on the right track or do I have this totally wrong? edit: I know that AN and DN work for bodies within the same SOI but they don't work when you're trying to launch into the plane of another planet. The autopilot seems to handle it just fine though so I'm wondering what data it's going off of. edit 2: Okay well I'm still not sure what the reference direction is but after messing around for a bit it seems that my craft always crosses the target's plane when LAN = targetLAN +/- 90deg. Not sure but it looks like the reference direction for a planetary SOI is the parent planet's prograde direction on its orbit?
-
[1.3.0] OPT Space Plane v2.0.1 - updated 29/07/2017
The Pink Ranger replied to K.Yeon's topic in KSP1 Mod Releases
Pretty cool man. Any plans for a cargo bay?