Jump to content

Manul

Members
  • Posts

    382
  • Joined

  • Last visited

Everything posted by Manul

  1. The question to all fellow victims of GCoD: how much RAM do you have and how many percents of it are consumed by KSP? Me: 32GB, memory usage while running KSP begins with 60% when the flight scene is loaded for the first time and gets above 70%-80% after a few hours
  2. It's a Green Clipboard of Doom.... no, two Green Clipboards of Doom! You are doomed twice, eject! eject immediately! restart the game before it's too late.
  3. I've seen it several times.... and had a crash to desktop some time after. Or to the black screen of death with a built-in speaker screaming. Mostly it happened after massive memory leaks or GPU running out of VRAM and getting deeper and deeper into RAM. Mostly it was caused by trying to run Parallax2 on GTX1050 while keeping graphical settings high.
  4. There used to be three versions of VV before: RPM-only, toolbar-only and all-in-one version (I guess it was a pain to update 3 mods instead of 1), with 0.8.7 only one remained. It's a long story why I'm still using RPM-only version. After KSP 1.4 and VV 0.8.7 update I messed up my RPM install so I had to revert and stick to 0.8.6 until I found the problem so I got used to it (there was RPM included into VV download together with JSI utilities and I mixed 2 RPM versions, as I discovered years later when I got more experienced with mods). Currently there are two reasons why I'm still using RPM-only version: background transparency and having no ClickThroughBlocker as a dependency. RPM-only version has a transparent background by default and doesn't need Vulkan's modifications to work with his holo-display. And CTB is somewhat incompatible with my control layout. After 1.7.1 update with all these juicy extra custom axis I had to add moar axis to my home-made hotas to control them all: a secondary throttle for VTOL engines, servo rotation controls. All these extra axis don't have a fixed 50% central point, their neutral position is 0. CTB locks all axis that aren't centered at 50% at scene load and force sets them to 50% (this is how the stock InputLockManager works, nothing can be done) so I get engines going half-throttle and servos violently rotating from 0 to 50% position every scene load causing the Scene Load Kracken. CTB has an option to disable it's functions but it's hidden within preprocessor directives, and I'm too lazy to remove dust from M$ Visual Studio, take source and compile it (and face the unforeseen consequences)
  5. Awesome! Makes me regret that I'm stuck to version 0.8.6.1 (it was the last RPM-only version of Vessel View)
  6. There are some major differences that lead to changes in craft design: 1) Armor has mass based on the part's surface area and armor thickness. Some old parts like tank/ship hulls and turrets that already had mass based on their default armor thickness became significantly heavier with proper armor. 2) Different armor types protect from different types of damage. But 30mm High Explosive is still a best anti-tank round as it used to be in BDA and BDAc (better at shredding tanks than railgun tungsten shells). And you can make GAU-8 shoot AP and HE rounds in the same belt as it does IRL. Or use 203mm nuclear artillery. Or throw asteroids with a gravity gun (good luck hitting any target smaller than Gilly) 3) radars, RCS and countermeasures are a subject to change between BDA+ updates so they would differ from BDAc (I don't know how exactly because I missed a few updates ) 4)Space combat had been fixed! Now it's possible to hit a target just in front of you with a ballistic weapon while being in non-kerbostationary orbit. Projectiles don't get spawned meters sideways from the muzzle and now they travel in a direction that the barrel is pointing, not sideways as they used to.
  7. This is what I do with docking ports. They allow to create loops. If I make a heavy ramp lifted by 2 pistons I dock them to the ramp. I even made a (mostly) rigid scissor-link structure for retractable floats to make a hypersonic seaplane, but this plane turned into a shapeless mess of parts due to Scene Load Kracken. This was already done by Kerbal Joint Reinforcement mod. These attachments are still wobbly-stretchy UnityJoints but by using more of them things get more rigid. Recoupling Bycouplers mod does a similar thing. This is not a fix for Kracken attacks caused by inaccurate physical calculations but it fixes sausageness.
  8. And with unrealistic joint model that doesn't create multiple joints. Let me explain why the "sausage tree" model is ridiculously stupid for everything except rockets (for rockets it works not so bad). Let's build a spaceshuttle. IRL the Big Orange Tank is attached to the shuttle in multiple points and is perfectly rigid. In KSP with it's tree joint structure it can be attached only in one point and wobbles like hell. This can be fixed by struts and still not a big issue. So let's build something like Cocnorde: IRL the wing is attached to fuselage all over the length of it's it's root chorde and is perfectly stable at 2 axis out of 3. In KSP it's attached only in 1 point somewhere in the middle and has all 3 axis of freedom. IRL these loooong engine nacelles are attached to the wing all over their length and in KSP they have only 1 attachment point and hang from the wing like dead snakes. Crafts inherited their tree physical structure from being a tree as a data structure. My biggest hope for KSP 2 was that it will change and we'll get a possibility to create closed rigid structures like a triangle without struts or docking ports to fix the loose vertex.
  9. There can be only one scientifically accurate explanation that doesn't involve aliens or evil curse: a problem with part config. Possible problems: no RPMComputer PartModule or multiple computers for one part. Can you copypaste here a patch that you use to add RasterPropMonitorComputer to the part cfg. It should look like this: @PART[My_Precious_Cockpit] { MODULE { name = RasterPropMonitorComputer } @INTERNAL { @name = Best_IVA_Ever } }
  10. In it's current state it totally destroys MAS functionality in all cockpits after the scene reload. Looks like MAS fails to save persistent variables for this cockpit when I exit the flight or switch vessels and fails to load any persistent variables for any IVA after this. Making and testing new props is pain.
  11. Did you add RasterPropMonitor computer or MAS Flight computer PartModule to the part you are making an IVA for? If indicators work normally but controls don't respond to clicking them, make sure that colliders aren't ostructed. They are shown as green boxes or rectangles in Unity editor. No. You have to set the whole GameData directory in PartTools menu to be able to spawn both spaces and props. If you don't give PartTools access to AsetProps folder it will not be able to spawn them. When you need to save an IVA you should select the space in the window on the left (make sure that you select a space, not props) and click "save to config" on the right window. PartTools will overwrite the selected IVA cfg and nothing more.
  12. It's a boring human way of doing space program. The kerbal way is to strap Jeb to the biggest SRB available and hope he will survive. These contracts are given by part manufacturers, the manufacturer pays for testing their product and doesn't care about anything else, testing the launch vehicle is up to the ones who build and fly it aka the player's space agency. No one will pay you for testing your own vehicle, the reward is a vehicle itself. Maybe it would be interesting to add some certification contracts that don't make profit but unlock the future missions. Like in the GAP contract pack there is a mission to land on the VAB helipad to be certified for helicopter-based search and rescue contracts. But the same rule is already used in stock: you don't get any orbital contracts until you reach orbit, and no contracts for new celestial bodies until you reach them
  13. It's up to you to make your missions serve a purpose in your program because no one else knows what is the purpose of your program. Customers will not pay for what you need, they always pay for what THEY need, this is how it works. After the early grindy days of career playthrough are over you can afford being picky with the contracts and accept ones that correspond to your own goals. For example I dislike bringing more and more trash to LKO, so I mostly ignore contracts for launching stations and satellites around Kerbin. The exception is when I need to test a launch vehicle or get more targets for space combat trials. The stock contract system isn't ideal of course, for me it's major flaw is that there is too few applications for rovers and aircraft because I like aircraft and rovers. And there is absolutely no application for naval vessels (okay, it's not a Kerbal Submarine Program, I know). That is why I use Contract Configurator with aircraft-based contract packs that allow me to get through the early career without grinding too much and turning low Kerbin orbit into a junkyard. My SPH folder turns into a junkyard instead due to countless semi-useless low-tech aircraft designes
  14. Unlike DCS world DLC aircrafts it's possible to get SC ships by in-game ways, so they aren't actual DLCs
  15. 1) Commercial missions give funds for exploration missions, isn't it a progress? SpaceX does a lot of commercial missions to afford the Mars mission you know. 2)Combining commercial and exploration aspects in one mission is makes both progress and profit 3)Contracts encourage to make more reusable crafts and interplanetary infrastructure to make future contracts and exploration go faster and cheaper, isn't this a progress? Just make it useful! Add ISRU, rovers (if there is gravity), probes, planes (if there is atmosphere), submarines (if there is liquid) and you get an exploration or refueling outpost. Also there are contracts to revisit old stuff like "make X experiments around base Y" (that's where the rover comes in handy) or "expand the base Y by adding more random stuff". Many crafts that had been collecting dust at some distant places for years (I mean human years not kerbal) got a new purpose when I took some contracts that I could use them for. With EVA construction repurposing old crafts for new goals is a really fun part of career gameplay. Like the mission where I launched an SSTO from my Laythe base, stole an RTG from an abandoned ship in Laythe orbit and attached it to a rover on Bop to complete the contract. Or an improvised mission from Pol to Eeloo because Eeloo was close to Jool at that moment and there was some work to do.
  16. I have experience with hunting rare resources in KSP with mods like Blueshift and The Gold Standart, and it isn't that exciting in long term perspective. The first missions to find Graviolium and Unobtanium and deploy bases for mining them were fun but as long as I had mining bases and reliable transports to get them home it became boring. Contracts suggest a bigger variety of activities than just scanning and mining, if they are done the right way. Resource gathering is too predictable to be fun, and with random contracts you newer know what you'll have to do next. I had to be really creative repurposing crafts in situ to complete some contracts without waiting years for a transfer window to send another mission. That is the reason why I have to keep a large variety of crafts at Laythe base, and these crafts are capable of performing a large variety of missions on Jool moons. Replacing all this variety with a boring fleet of cargo freighters is not exciting by any means.
  17. They made people pay for a dream that we all have after playing 90s and early 00s spacesims like Starlancer, Independence War or Privateer: get out off a pilot seat, take a walk around your ship, dock to the station and explore it's interiors, land on a planet and explore the whole planet. We began to dream about a game like Star Citizen decades ago, so another 5 or 10 years don't make a difference.
  18. There is just one cause: both games use the same physical model, craft is a tree structure of rigidbodies connected by UnityJoints. This approach proved to be faulty in KSP 1 and now it's used in KSP 2 with exactly the same result. The cause of a problem is built-in Unity physics that doesn't simulate multiple rigidbody connections correctly, especially with huge mass differences between connected parts. Fixing this issue the right way would require writing a new physical model from scratch and the devs were not given enough time for this.
  19. What is the drama of Star Citizen? Except of being in development for over 10 years
  20. Most of this magic comes from MOARdV Avionics Systems (MOARdV is a true magician too) , but there are misterious things like collimated HUD that are another sort of magic I can not understand.
  21. MOARdV Avionics System + ASET Props/Avionics Because of this:
  22. Making it 5 million times stronger doesn't help either. If it was this simple there would be no need in spamming hundreds of extra joints like autostruts or KerbalJointReinforcement do. And there is an alternative to the tree structure we have in KSP: a grid structure. It's more rigid by it's nature than a tree where each parts doesn't connect to anything except it's parent or child and each branch of a tree just wobbles freely.
  23. No alternative to "sausage tree" physical model? No alternative to connect rigidbodies other than using the faulty UnityJoint and "fixing" it by just spamming more and more UnityJoints?
  24. No idea why ModuleIntake is throwing exceptions while there is no ModuleIntake on these engines, but I found why Buffalo2 cargobays do not produce dragshielding. Also fixed dragcubes for cargobays when they are in the middle of a stack. Made a pull request on github Guppy submarine became significantly faster with proper dragshielding
  25. KK statics doesn't depend on KSP version, it only depends on Kerbal Konstructs version. What exactly is not working in KSP 1.12.x?
×
×
  • Create New...