Nicky21

I have a problem and I'm not sure if this mod causes it. I've had this problem before, but never this bad. I plot a trajectory to ceti from gael, i get close to a periapsis of about 50 km then when i warp to a closer point my periapsis is now 600 something km. Sometimes i even lose planet intercepts this way. 1) How do i figure out which mod is the culprit ? 2) I suspect that it's the large distances in the new GPP + GEP map that are causing such floating point errors. If i unintstall GEP will this break my save and/or aleviate the issue ?

I have a question: If i use the asteroid factory do i get more ore out of an asteroid compared to the stock mining drills ? The factory is very appealing as it allows me to produce mining stations X3 like

This is an extraordinary mod. Squad should make this part of stock or something. Thank you !

Awesome news ! This mod completely changes the way i play ksp !

When using the options to switch OPT tank in flight this also modifies the mass of said tank, thus increasing / decreasing DV. While I love the option of doing changes in flight, this is a good way to cheat some extra DV. Can you make sure the tanks have the same mass ?

I have a suggestion. I dunno if this is the place to leave it. Something for the end game. Artificial Gravity. An extremely high tech research along the lines of warp drive that gives you a loooot of habitation. Somethign that requires decent power to run. And by decent i mean nuclear reactors won't cut it.

Yeah, that's the one.

It will do this again, and when it does I'll post the log.

It's not just an recompile issue. I tried the mod and it crashes on 1.4.5 .

Somewhat of a bug report: The lynx attachable thruster does not get reported by the mod "kerbal engineer redux" when calculating delta-v and other stuff in the vab. Also : the decoupler: enable staging does nothing. It does not enable staging.

Mouse worked on the toolbar menu, it only "dissapeared/; my context menu on the map. there was no need for hotkey. Log: https://ufile.io/nis0p But as i said, this was hour s ago and i restarted twice since.

I created a node to go from Iota to Ceti. since it was a tricky maneuver i enabled the precise mod editor. i finished my course correction then closed the precise window. then i tried to click on the trajectory to warp to next maneuver and nothing happened.my mouse click was not working any more. The small sphere showed up on the trajectory following my mouse but when i click nothing. If i double click another body to focus view, again, nothing. I could not switch vessel , focus view or warp since the menu will not appear. Quick save - quick load will not work. What did work is to reactivate the precise maneuver UI then i could suddenly click on the trajectory and get the warp to menu. After that i deactivated the ui and things went back to normal. This bug for me is a frequent occurrence. Where do i find the log ? And btw, this happened a few hours back, i kept plying from then on, i don't know if the log is still there.

There is a bug with the UI of this mod. ometimes, after i st up an node with the advanced tool i can no longer create maneouver nodes or stop time along the trajectory. I hover on the trajectory, i see the bulb, but when i click nothing happens, no menu, no thing.

The Hades engine causes a game freeze when it flames out. The message i get is that the core temperature is exceeded, engine is shutting down then all the stars dissapear, al teh shps dissapear, the ui is present but nothing is there. If i try to reload, the game crashes.

There is a bug with the mk2 tricoupler. the big engine mount of the tricoupler frequently loses its connection node after a save. I try to take out the big engine in the middle and replace it with another engine, but the node is gone after removing the original engine. The two smaller nodes pose no issue. However, adding a new tricoupler works as intended, there are all the nodes you would expect.

How do i figure out wich one of hte oe hundred mods are causing my game to lag when switching to map mode? FPS are fine when i look at th eship but when i move to map mode it slows down a bit. The console shows no (red) errors. Are there debugging tools that tell me which mod takes the most cpu ?

What variable do i need to change in order to put a bit more fuel in teh procedural wing?

Disregard. Apparently the scienceMultiplier variable needs to be an natural number, not a float. Aparently changing it form 1.5 to 1 HAS teh result i needed.

Yeah, i guess ts the OPT mod that's outdated.

I tried to make the science lab less op by nerfing teh science you get. I changed "scienceMultiplier" variable form 5 to 1.5 , however whenever i send some crew report to the lab i still get 5 data worth of science. Is there a trick to this ? Am i not modifying the correct variable ?

I hae the exact problem as well. I have a lot of mods installed and some of them are causing slowdowns when in map mode. The weird thing is the when i look at the ship the fps are fine, just the map is slown down. I would really like to know if there's a way to figure out which mod is taking so much cpu.

Eventualy i figures it's the way the wings are configured in a certain mod, so teh problem it's not this mod.

I found some kind of bug. When using this mod the FPS in map mode drop significantly. Like 30% significantly. It took me a while to identify which mod was doing that but after I uninstalled this mod the fps came back to normal. It does not matter if the vessel has a docking port on it or not, it happens to simple probes as well. Note FPS drop s only when displaying the map, not when looking at the vessel itself. Let me know if you need files/screenshots or something.

Can you take a look at the wings in OPT legacy? I noticed that using tweakscale on them does not alter the COL at all, while using the Delta Deluxe winglet does alter the COL. Then i opened the cfg files and I saw that squad made some changes to how they define wings, but i can't figure out what is what.

I'm not exactly sure what this mod does. I noticed that if i use tweakscale to scale down some wings the COL stays in the same place as before, even though is should definitely be moved. I thought this mod solves that issue. Does it not ?