Fastfishy2

you have no idea how long I did the same thing lol. Didn't find a single KSP2 specific report on this and I was crapping my pants thinking it was something on my end. Yours looks basically the same as mine, maybe slightly more severe, but the fact it's happening on an RTX 3060 as opposed to a 4070 shows it really must be a game thing.

Hi everyone. I've been having an issue with DeepFreeze and KSPI-E parts crashing the game but only when they are on the same craft and I then move that craft to the launchpad. I narrowed this down to the KSPI-E science lab part, and the 1.25m single-kerbal cryopod part. Having them connected, directly or through other parts, on the same ship causes the camera to pan below the launchpad as soon as the craft has loaded and the game then crashes, with the crash handler GUI coming up, after which the game closes to desktop. Is there a way to resolve this issue? Log file: https://www.dropbox.com/scl/fi/1iub96l1phgkx6303agme/Player.log?rlkey=lkr8uvpuo1wc8ny2vb4n79cdr&dl=0

Thanks mate. Don't need to worry about my shiny new 4070. Have a good one.

Oh righto. They don't mention green and purple flashes. But it seems AA is buggy.

oh thank god.. I was getting worried. Never heard of this bug before, but granted, I'm not super involved in the forums as I used to be. Could you point me to where it is listed? Thank you again for taking the time to answer.

Already submitted a bug report for this one but I'm wondering if anyone else has come across this issue. Basically, anti-aliased edges of distant terrain objects can sometimes have green + purple dots moving along them and sometimes these dots cause green or purple flashes. Only happens on distant terrain, changing resolution & GPU load doesn't seem to make much difference, and I can't reproduce the bug in heavy benchmarking, stress tests, or any other game. Still kinda worried it might be my PC though. Anyone else had this problem? Photo Example on Imgur, because I don't know any other way to host / share files :(

Reported Version: v0.1.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home | CPU: Ryzen 7 5800X3D | GPU: GeForce RTX 4070 12gb | RAM: 32gb DDR4-3200 CL16 RAM Recently upgraded to an RTX 4070 and I'm seeing these weird green / purple dots that move with the anti-aliasing on distant terrain objects, and sometimes flash their respective colours. Only happens on distant terrain, not close terrain or any part of the craft. Multiple high-stress benchmarks and testing in other games seems to confirm it is not a hardware problem. I have the latest NVIDIA drivers installed. Included Attachments: ksp2_x64.exe2023_06.11-10_01.59_01.mp4

Hi, whenever I run this I have absolutely atrocious FPS problems. My system has an i7-8750H hex-core processor and a GTX 1050 4gb (it's a laptop). Have confirmed no downclocking, overheating, or anything similar is happening and the Nvidia GPU is definitely in use. Problems are especially bad whilst in atmosphere. Any help is appreciated, and if you need me to attach any files just let me know which ones.

Yeah it isn't trapped inside a star or anything, it's just weird. Some of the other stars (Karkua for instance) also only show up black with a white outline.

Yeah the space center terrain glitch. Also has the issue of not being able to click some buildings at certain angles. I also tend to get the white sky effect when flying / eva on kerbin, will see if this is still the case. If kerbin somehow HAS managed to dump itself inside a sun, how do I fix that?

Hey @StarCrusher96 sorry I sent you a DM about this earlier but the log file was pasted (mistake #1) and way outdated (mistake #2) and without relevant info (mistake #3) or reproduction info (mistake #4) Really severe graphical bug. Help appreciated. Not sure if this is the right place to put it. Version: KSP 1.4.5 x64 Windows 10 Launching manually via KSPx64 Using Kopernicus 1.4.5-4 and latest release of KSS Image of the issue: https://imgur.com/a/QuMGWUg output_log: https://www.4shared.com/office/GjMqNNbFgm/output_log.html Would be really awesome if I could get help with this. Happens regardless of whether I use a bunch of mods or just this on its own.

Problem solved. Thank you!

Alright, I'll try that today.

Tried it in x64 mode, no difference. Funny thing is, I have games that use over 4x more RAM and are much more intensive, doesn't happen with them

I think what it means by 0MB memory is that it has 0mb ALLOCATED memory left to it. Because it then shows later down that there is about 15.2GB of memory left. I'll check my antivirus and also check what mode KSP is running in.

So on my new laptop, I've encountered an issue lately with KSP. When I press F12 to take game screenshots through steam, it usually works a couple times but it may work once and then crash a minute after, or crash after I take about 2-3 screenshots in flight. I've tried repeatedly taking screenshots in my other steam games such as Rust and Fallout 4, no crashes no matter how many I take. Error.txt: Unity Player [version: Unity 5.4.0p4_b15b5ae035b7] KSP.exe caused an Access Violation (0xc0000005) in module KSP.exe at 0023:000001c4. Error occurred at 2016-11-13_100148. D:\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Harrison. 25% memory in use. 0 MB physical memory [0 MB free]. 0 MB paging file [0 MB free]. 0 MB user address space [1520 MB free]. Write to location 000001c4 caused an access violation. Context: EDI: 0x2f6fc1ac ESI: 0x00000000 EAX: 0x000001c4 EBX: 0x0219f268 ECX: 0x00000001 EDX: 0x2f6fc040 EIP: 0x000001c4 EBP: 0x0219f258 SegCs: 0x00000023 EFlags: 0x00010202 ESP: 0x0219f230 SegSs: 0x0000002b Bytes at CS:EIP: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? And then it goes on and on Output_log.txt: Initialize engine version: 5.4.0p4 (b15b5ae035b7) GfxDevice: creating device client; threaded=1 Direct3D: Version: Direct3D 9.0c [nvd3dum.dll 21.21.13.7570] Renderer: NVIDIA GeForce GTX 960M Vendor: NVIDIA VRAM: 2018 MB (via DXGI) Caps: Shader=30 DepthRT=1 NativeDepth=1 NativeShadow=1 DF16=0 INTZ=1 NULL=1 RESZ=0 SlowINTZ=0 ATOC=1 and then a million lines of... stuff Any help appreciated.

Okay, so: - It's a known issue for Nvidia 8xxM and 9xxM chipsets in laptops because of the hybrid graphics config. Installing the latest driver did not help however disabling V-sync but leaving the frame limiter at 60 resulted in a fix to the problem. Happy to report my KSP is running normally now.

Hi, I don't know how to put the output_log or other files into my replies (sorry!) After some research, diagonal screen tearing seems to be an issue with numerous Nvidia based gaming laptops and chipsets such as the GTX 960m which I have, although not all with this chip are affected. I have seen at least one person say that kerbal space program is one of the select games that can be affected by this. My specifications: i7-6700HQ 16gb DDR4 2133mhz GTX 960m 2gb GDDR5 128gb M.2 SSD 1tb HDD @ 7200RPM 1080p 16:9 screen (14") I am running the latest steam version of KSP non-modded.

I am using a brand new Gigabyte P55G laptop. It has a GTX 960m GPU and is using the drivers it shipped with on recommendation of my local shop. Before I start, may I state that this issue appears to only affect the gameplay of Kerbal space program. No other games seem to be affected while playing. This is also my second laptop of this identical model after the first one was taken in for a different issue. I'm fairly convinced this is a software issue. What happens is I will get a horizontal line distortion from the top left hand corner down to the centre of the screen and there it will stop. Seems to be noticeable when moving camera view. However it seems I am unable to capture it in a screen shot. I would think it was a hardware issue if it was not only affecting this game and it's also the second laptop of this model Any help appreciated. I can provide more details if needed.

As with others on this thread I would also like to thank squad -For the effort they have put into this game, transforming it from what I and other people knew it as a few years ago, to what it is now. -For creating a game like no other, and making it what it is. -For doing what not all devs are prepared to do: get their boots dirty and wade into all the community suggestions to listen and act on it -And for adding airbrakes and all the cool stuff that came with 1.0 And a whole lot of other things, but one thing is for certain, 2 or so years on and I can still say $40 well spent. very well spent.

if you have ever made a mothership or a colony ship, you know these things are huge. post pictures of your mega-ships, and if you want, what they were used for, whether you assembled them in orbit or were determined enough to launch them one-piece with too many rocket engines. this is my minmus colony ship, called CCCP Premier Dubienken, and it is the largest ship i have launched (legit) to date. it has 3 skipper engines, a cargo bay housing a small lander, two living compartments, and two docking ports, as well as a spotlight array mounted underneath. as of these photos it is waiting in orbit for a tanker to come and top-up its fuel tanks for the trip to minmus. once it has landed a lander on minmus i may decide to either leave it there as a staging point or i may use it as a all-purpose cruiser for exclusive use in the kerbin moon system. i honestly did not think the launcher concept would work but after a bit of tweaking, it worked like an absolute dream. launching the thing:

ok, so we've all heard of the infamous Duna rovers. but what about mun rovers? post your mun rovers and if you want, any challenges/failures/extremely embarrassing failures/ that you've had with it. i'll start off: this rover is a four-wheeled, solar-powered mun rover called rovemax mk.1S (S meaning Solar) and it is my first rover that did not fail either while landing or the lander not being able to accommodate the rover properly, or the rocket failing and putting me off for another 2 months. mind you, it almsot did becuase i managed to land on the very edge of a sheer cliff. thankfully i was able to learn rover-wrangling rather quickly and managed to roll away from the lander in one piece. and as i was rolling up to the sky-crane-debris it exploded about 200m away from me and i found this rolling away from it. yay, a donut! mission success!

i did use shuttles once, after trying and failing so many times i found a design that worked. and it worked well. the only thing i stuffed up was the landing and that was (almost) entirely my fault. it was small for a shuttle, but i managed to deploy a small military spy satellite with it. the satellite had a romfarer lazer system module so it could zoom in on targets. here is another shot, in orbit. the kerbal is worried for a good reason: he knows my landing skills were so bad that at the time that except for a few flukes, i could not land most aircraft i built.

okay, my instuments aren't working so [THREAD ABANDONED] sorry for the waste of forum space i was actually wanting it to be a lot more useful

also i shall list what equipment is use, i will use mod equipment such as panda jager's water sensor. if i cannot gather any viable data from complex instruments due to it bieng sandbox i will mark this thread with an [THREAD ABANDONED]