diomedea 703 Posted January 6, 2017 Share Posted January 6, 2017 1 minute ago, Sharpy said: 1.62^2=2.7225 so two classes up seems to be it. Gonna wait some time for new asteroids to spawn - while radius changes dynamically, mass seems to be assigned at spawning time (basing on radius) and saved. The fixed patch got size in check, but the asteroid remained as heavy as before. Allow me to correct the above a bit, could be I wasn't clear before, radius goes with the cubic root (not the square root) of volume. 1.65^3 = ~4.5. Can't tell about the patch; but certainly each asteroid when discovered has a size assigned (not exact mass, that is determined only after it enters the bubble if I'm right) Quote Link to post Share on other sites
Sharpy 1,977 Posted January 6, 2017 Author Share Posted January 6, 2017 22 minutes ago, diomedea said: Allow me to correct the above a bit, could be I wasn't clear before, radius goes with the cubic root (not the square root) of volume. 1.65^3 = ~4.5. Not volume. I have no direct control over volume. Class. I can set radius multiplier. So, how much larger radius does class G have than class E? Quote Link to post Share on other sites
diomedea 703 Posted January 6, 2017 Share Posted January 6, 2017 Fine, got what you meant now. Yes, 1.65^2 = 2.725 times the radius. Quote Link to post Share on other sites
Tyko 2,403 Posted January 6, 2017 Share Posted January 6, 2017 @Sharpy, given that insight about density being too low, would there be a way to use MM to increase the mass without changing the size of the asteroids? The previous MM config you shared increases the size. This may give us more "realistic asteroids" Quote Link to post Share on other sites
Sharpy 1,977 Posted January 7, 2017 Author Share Posted January 7, 2017 @PART:HAS[@MODULE[ModuleAsteroid]] { @MODULE[ModuleAsteroid] { @density *= 33.3333333333333 // Stock asteroids will have density of 1.0 maxRadiusMultiplier = 5.0 //Default is 1.25 so up to four times larger } @density *= 33.3333333333333 // Stock asteroids will have density of 1.0 } This is Roverdude's ART patch for the asteroids. Quote Link to post Share on other sites
Tyko 2,403 Posted January 13, 2017 Share Posted January 13, 2017 (edited) On 1/6/2017 at 6:03 PM, Sharpy said: @PART:HAS[@MODULE[ModuleAsteroid]] { @MODULE[ModuleAsteroid] { @density *= 33.3333333333333 // Stock asteroids will have density of 1.0 maxRadiusMultiplier = 5.0 //Default is 1.25 so up to four times larger } @density *= 33.3333333333333 // Stock asteroids will have density of 1.0 } This is Roverdude's ART patch for the asteroids. I've been toying with a mix of your and @RoverDude's configs. When I tried yours, which increases size, I found a lot of issues with the collision boxes. Maybe it was just bad luck, but in the half dozen encounters I tried it appeared the the collision boxes were less accurate relative to the asteroid skin. I'm thinking that increasing the size just exacerbated the collision box issues the asteroids already had. Here's the config that I've settled on: Spoiler @PART:HAS[@MODULE[ModuleAsteroid]] { @MODULE[ModuleAsteroid] { @density *= 1 // Stock asteroids will have density of 1.0 maxRadiusMultiplier = 5 //Default is 0.95 minRadiusMultiplier = 5 //Default is 1.25 } @density *= 1 // Stock asteroids will have density of 1.0 } This config gave me a class A @ 500 tons, Class B @ 2400 tons and a Class C @ 11K tons. Of course there's a random factor, but if these are somewhat representative, it would make Class A and B manageable, but anything larger a real challenge. As a side question...do ALL asteroids use the same model? Edited January 13, 2017 by Tyko Quote Link to post Share on other sites
Sharpy 1,977 Posted January 13, 2017 Author Share Posted January 13, 2017 1 hour ago, Tyko said: I've been toying with a mix of your and @RoverDude's configs. When I tried yours, which increases size, I found a lot of issues with the collision boxes. Maybe it was just bad luck, but in the half dozen encounters I tried it appeared the the collision boxes were less accurate relative to the asteroid skin. I'm thinking that increasing the size just exacerbated the collision box issues the asteroids already had. [...] This config gave me a class A @ 500 tons, Class B @ 2400 tons and a Class C @ 11K tons. Of course there's a random factor, but if these are somewhat representative, it would make Class A and B manageable, but anything larger a real challenge. As a side question...do ALL asteroids use the same model? Asteroids have their collider much simpler than the actual model. The discrepancy is directly proportional to the asteroid size, so obviously larger asteroids will have it worse. By giving the asteroids the same min. and max. size, you've removed the random factor The randomness is still in ore content (some 70-90%) but not in size. All asteroids are procedurally generated, you have a 'seed' in your save file which decides what is the asteroid looks like. Regardless, they all look very similar. There's a different layout of bumps, holes, hills and ridges, but they all have bumps, holes, hills and ridges, and it's quite hard to tell them apart just by looks if you don't remember the specific layout (and why would you do that?) Quote Link to post Share on other sites
Tyko 2,403 Posted January 13, 2017 Share Posted January 13, 2017 (edited) 4 hours ago, Sharpy said: Asteroids have their collider much simpler than the actual model. The discrepancy is directly proportional to the asteroid size, so obviously larger asteroids will have it worse. By giving the asteroids the same min. and max. size, you've removed the random factor The randomness is still in ore content (some 70-90%) but not in size. All asteroids are procedurally generated, you have a 'seed' in your save file which decides what is the asteroid looks like. Regardless, they all look very similar. There's a different layout of bumps, holes, hills and ridges, but they all have bumps, holes, hills and ridges, and it's quite hard to tell them apart just by looks if you don't remember the specific layout (and why would you do that?) hmm..thanks for that tip. I've spent the last few hours messing with the numbers, but haven't quite understood how they affect the final size. part of the problem is that I only take a few random samples with each change - a A or 2, a C or 2 and a couple of E's. Can you explain how the various settings work? I'm assuming "Density" increases mass, but not size, while the other two limit min and max sizes. Although I'm confused that the default Max is 0.95 while Min is 1.25 Edited January 13, 2017 by Tyko Quote Link to post Share on other sites
Sharpy 1,977 Posted January 14, 2017 Author Share Posted January 14, 2017 4 hours ago, Tyko said: hmm..thanks for that tip. I've spent the last few hours messing with the numbers, but haven't quite understood how they affect the final size. part of the problem is that I only take a few random samples with each change - a A or 2, a C or 2 and a couple of E's. Can you explain how the various settings work? I'm assuming "Density" increases mass, but not size, while the other two limit min and max sizes. Although I'm confused that the default Max is 0.95 while Min is 1.25 Sizes are radius multipliers, range between smallest and largest of given class. I'm not sure what the baseline is but the mass is asteroid volume (dependent on third power of radius) times density. So, Radius is the original "generated/regulated" value (this is what 'asteroid spawner' creates basing on config and random number), and the volume and mass is calculated from that. Since we know mass is related to e^(1.5 x class ), but mass is a derived value, uh... the formula for spawned radius will be rather nasty. Quote Link to post Share on other sites
Nicky21 54 Posted June 17, 2019 Share Posted June 17, 2019 On 1/14/2017 at 6:10 AM, Sharpy said: Sizes are radius multipliers, range between smallest and largest of given class. I'm not sure what the baseline is but the mass is asteroid volume (dependent on third power of radius) times density. So, Radius is the original "generated/regulated" value (this is what 'asteroid spawner' creates basing on config and random number), and the volume and mass is calculated from that. Since we know mass is related to e^(1.5 x class ), but mass is a derived value, uh... the formula for spawned radius will be rather nasty. Has this idea been made into a mod ? I want bigger asteroids myself ! Quote Link to post Share on other sites
CarefreeFish 0 Posted July 7, 2020 Share Posted July 7, 2020 On 12/25/2016 at 9:26 AM, Sharpy said: Reading the files of ART, and KSP API if we sacrifice class A and B (I never really found any use for these), @PART:HAS[@MODULE[ModuleAsteroid]] { @MODULE[ModuleAsteroid] { maxRadiusMultiplier = 19.08 //Default is 0.95 minRadiusMultiplier = 25.1 //Default is 1.25 } } this should simply bump all the asteroids two classes up size-wise. "New class C" would be "Old class E". New class E would be around 17 to 76 thousand tons. Further testing required. How can I find these parameters？ Quote Link to post Share on other sites
Clamp-o-Tron 867 Posted July 8, 2020 Share Posted July 8, 2020 9 hours ago, CarefreeFish said: How can I find these parameters？ This is a module manager patch, which will modify the values without actually changing the files. Download the mod, and copy/paste the text into an empty text file in your GameData folder. Make sure that the file extension is .cfg! Quote Link to post Share on other sites
Souptime 367 Posted July 8, 2020 Share Posted July 8, 2020 NEW IDEA Z CLASS ASTEROIDS Quote Link to post Share on other sites
CarefreeFish 0 Posted July 8, 2020 Share Posted July 8, 2020 10 hours ago, Clamp-o-Tron said: This is a module manager patch, which will modify the values without actually changing the files. Download the mod, and copy/paste the text into an empty text file in your GameData folder. Make sure that the file extension is .cfg! Got it. Thanks very much! Quote Link to post Share on other sites
Clamp-o-Tron 867 Posted July 8, 2020 Share Posted July 8, 2020 13 hours ago, Souptime said: NEW IDEA Z CLASS ASTEROIDS That’s Gilly. Quote Link to post Share on other sites
Souptime 367 Posted July 8, 2020 Share Posted July 8, 2020 NEW IDEA Z Z P L U S A S T E R O I D S Quote Link to post Share on other sites
Clamp-o-Tron 867 Posted July 15, 2020 Share Posted July 15, 2020 On 7/8/2020 at 12:09 PM, Souptime said: NEW IDEA Z Z P L U S A S T E R O I D S That’s Dres Tylo. ^ | | What’s a Dres? Quote Link to post Share on other sites
Souptime 367 Posted July 15, 2020 Share Posted July 15, 2020 NEW IDEA Z Z Z P L U S A S T E R O I D S Quote Link to post Share on other sites
Sharpy 1,977 Posted July 17, 2020 Author Share Posted July 17, 2020 On 7/8/2020 at 7:31 PM, Clamp-o-Tron said: That’s Gilly. Sorry, I've already shown calculations Gilly is Y class. You were close though. Quote Link to post Share on other sites
Clamp-o-Tron 867 Posted July 17, 2020 Share Posted July 17, 2020 8 hours ago, Sharpy said: Sorry, I've already shown calculations Gilly is Y class. You were close though. A joke. Detect sarcasm. This is also sarcasm. Quote Link to post Share on other sites
redrem 6 Posted November 22, 2020 Share Posted November 22, 2020 (edited) I have copernicus and sigma installed at 1.10 and redux. Asteroids with signatures from F to I are generated on the map by themselves. But when they approach, they have the mass and dimensions of the E class. Who saw this? And if somewhere in these mods new dimensions are already laid, how to correct the Phys. generation to match the size of the class. Edited November 22, 2020 by redrem Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.