- #BEAT SABER MOD MANAGER 1.3.0 INSTALL#
- #BEAT SABER MOD MANAGER 1.3.0 DRIVER#
- #BEAT SABER MOD MANAGER 1.3.0 FULL#
- #BEAT SABER MOD MANAGER 1.3.0 MODS#
- #BEAT SABER MOD MANAGER 1.3.0 SOFTWARE#
Finally, purely graphics options shouldnt make for a noticeable slowdown.If you haven’t played custom songs yet and are just getting started with Beat Saber, we’re excited for you.
Try reducing terrain detail if FPS are not yet high enough.
Linux's issues with KSP apparently stem from CPU-intensive workloads.
#BEAT SABER MOD MANAGER 1.3.0 MODS#
Check with and without them - I've had problems with mods using large amounts of png files, for example. A mod that doesnt appear to hurt fps on Windows may do so on Linux. Some mods are coded with only Windows in mind, not Linux. Disable the driver's vsync ("sync to vblank") and cap your fps from settings.cfg instead.
#BEAT SABER MOD MANAGER 1.3.0 FULL#
Check that your CPU is running at full power when running the game. Some distros handle CPU power states in a weird manner, prefering power-saving states over performance modes.
#BEAT SABER MOD MANAGER 1.3.0 DRIVER#
USE nvidia's threaded optimizations, which only work for the propietary driver (forget Nouveau, it's not meant for gaming) - this will give you a nice boost to fps. Use Openbox/LXDE/XFDE/MATE and/or disable it.
#BEAT SABER MOD MANAGER 1.3.0 SOFTWARE#
They are implemented differently than windows gdm and its software counterpart, and they WILL slow your game down. Ive delved into that subject for months now, and all ive come up with is this: -DO NOT run KSP along with a composting window manager.
#BEAT SABER MOD MANAGER 1.3.0 INSTALL#
Do you have a special config for that in your playthrough or am i just thinking lazy? Well you could always install an LXDE linux distro (which only take 200 to 300 mb of ram and are FAST) to make up for that pc's lower capabilities, and then you would not need to use ATM to play the game, even with a few mods! Make sure to install the texture reduction packs in that case tho
Really looking forward to more videos! Ive only played with the stock Kerbol system so far and I'd really like to try that 6.4 upscaled config, though looking at the dV requirements it seems i'd have to 'rebalance' most of the existing (vanilla and mod) parts to bring the tanks and engines in line with the new config, so i can still go to other planets and do crazy stuff without too much launches and orbital assembly. totm september : I've been really enjoying your KSP Rescaled series, i subbed to your channel only a couple weeks ago but ive been through most of your KSP (and Factorio's) content in that time - few 'let's players' take their time and actually enjoy what they are doing while showing all the good stuff these indie games have to offer.However, when I replaced that config with this one, the game crashed during the first launch, before landing:ĬPU: Intel(R) Core(TM) i7-3770 CPU 3.40GHz (8) By using only the following config (with the relevant textures ofc) the game did not crash after several launches to LKO and long deorbits: SECOND EDIT: I did some more testing, all with EVE-Redux1.11.2.1. I did find this in the logs after using it:Īt () in :0Īt () in :0Īt () in :0 These crashes never happen without EVE, even with Scatterer installed which I had been using alone without issues, before replacing it with EVE, and which I reinstalled to check if it would ever crash by launching and deorbiting stuff and it didn't. The difference is that with Redux this happens consistently after a while in the atmosphere, while with the others I can launch and deorbit some stuff before it crashes. NullReferenceException: Object reference not set to an instance of an objectĪt Atmosphere.CloudsPQS+d_28.MoveNext () in :0Īt ( enumerator, System.IntPtr returnValueAddress) in :0ĮDIT: This crash also happens with EVE maintenance 1.10.1-3 and original EVE 1.8.0.2. I found this in the logs, the only error(s) but not placed last on the log, may be related: Mods: EVE-Redux1.11.2.1, Spectra 1.4.0, Kerbal Alarm Clock. This occurs consistently a short while after launching a rocket (around the time when leaving the atmosphere), when changing to map view, staging, or just moving the camera a lot. This does not happen without the mod, nor with with EVE 1.10.1-3 (the latest "maintenance" version). The screen turns black, game is unresponsive but audio keeps playing on a loop, can't do anything but reboot. Hi! I'm getting consistent hard crashes with this mod on Linux.
0 kommentar(er)
