pleroy

This is not how Principia works. Gravitational forces are applied to the vessel, not to its parts. Vessels can have hundreds of parts, the performance would be horrendous. Consequently, there are no tidal effects.

Congratulation for discovering that orbits around L2 are unstable. I invite you to consult Wikipedia for details about this instead of trusting what you remember reading. Note that "12th generation i5" covers a broad variety of processors, including both desktops and laptops, so it's impossible to say if that's a good choice for Principia. In general the more cores, the better. Also, we recommend destroying debris and disabling the asteroids as they burn CPU for little value.

The Kopernicus configuration here needs to be put somewhere in the GameData folder (anywhere), and to have the extension .cfg. You should not have to mess with anything else. One important point is that you must create a new save. The configuration of the solar system is recorded in the save the first time it is created, and the .cfg files are not re-read after that.

Believe it or not, we don't do N-body physics for landed vessels.

There is no "simplified" version of Principia and there won't be because the time is not spent where you think it is. The interactions between celestial bodies cost virtually nothing: we can compute about 6 months of interactions per second, which corresponds to warp 15,000,000. Nobody is limited by that. The problem with large spacecrafts is that Principia needs to position every single part at every frame. If your vessel has, say, 1000 parts, that leaves us with 40 μs for each part. That's not much, and sure enough we will sometimes slow down the game. We are aware of the problem and there is an issue for that (#3230) but unfortunately, there is no easy solution.

Thanks. I created issue #3697 to track this. I verified that I could uncompress the journal. PS: Don't expect a quick resolution, it's a big journal and probably a hard problem.

Maybe. Maybe not. First, the speed-up only concerns the rotating-pulsating frame where we display equipotentials. Second, if you have many cores, it won't make much of a difference, equipotentials will burn some of your cores but won't affect interactivity. So we are left with the case where you don't have many cores (2-4) and you display equipotentials, then yes, there will be an improvement on warp speed.

This is not the log that we need. As a matter of fact, for such a tricky bug we'd need a journal taken while the problem happens. Details here. ETA: We would actually very much like to be able to investigate this issue. We have had a report years ago of a similar problem but we never managed to get to the root cause. Interestingly, there was a Service Module. So maybe that tells us something. You would help us greatly by providing a journal.

We don't test on macOS as we don't have access to macOS machines. We just build for it. There are people using macOS on the Principia Discord channel. You might try to ask there. We haven't heard of problems so far, so it might be your install.

We constantly recompute them, but not at every frame, because it takes may be one second to do the computation. You might observe that they update in a somewhat janky manner. And we don't try to do things incrementally, because that way lies madness. That's good feedback. I'm sure that there is room for optimization, but getting something out was our priority.

How many cores do you have? The equipotential computation is completely asynchronous so it should be invisible if you have enough cores. We will work on optimizing the equipotential computations in future releases. However, I don't see us having a setting for the number of equipotentials, the heuristics to decide what to plot is already complicated enough. Edit: Actually, computing the equipotentials is cheap (comparable to computing trajectories, which we do much faster than 50 fps for a single trajectory). The really expensive part is the computation of the maxima of the potential, because that's a global optimization. But the whole point of the feature is to locate these maxima, so there is no easy way out.

Sounds like a bug. Created #3569 to track this.

Thanks for reporting. I created issue #3473 to track this.

Did I say Player.log? No, I didn't. I cannot make sense of your post. Reminder: for anyone wishing to report bugs about Principia, please follow the instructions in the FAQs.

There is a mechanism to override the version check. No support if you do this.