-
Posts
17,670 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by sal_vager
-
Windows 10, -opengl or -dx commands?
sal_vager replied to SmashBrown's topic in KSP1 Mods Discussions
The unity game engine doesn't have any support for DirectX12 yet, so there is no command for it. -
Don't know where to put this really, so moved to Gameplay Q's. As long as your craft returns to normal when reverting to 1x speed everything's fine, there's a reason why physwarp only goes up to 4x and for the warning.
-
I have not used Windows 10 yet, I'm not really planning to, but I am seeing some odd issues in the Support section from Windows 10 KSP players. Most probably stem from Win10 needing newer graphics drivers, and probably has only partial Dx9 support, openGL as well seems broken on Win10 for some. Also, not much actual science in here, this is better in the Lounge.
-
You might have more luck on a Microsoft support site if you're having issues, there's usually some cause, also this isn't really science. Moving to the Lounge
-
Start Game Sub-menu doesn't work
sal_vager replied to byedidia's topic in KSP1 Technical Support (PC, unmodded installs)
It looks like maybe there's some files missing, something the Unity engine does is use local URL's to find data files. Check your saves folder, make sure you have Training and Scenarios, if you made a save already there should be a Default folder as well. The Default folder should contain a persistent.sfs and both a VAB and SPH folder, if any of these are missing the game can fail to load anything on the New Game screen. -
Terrain lighting
sal_vager replied to Vkihyone's topic in KSP1 Technical Support (PC, modded installs)
In your settings there is a slider for maximum point lights, if this is not high enough then not all lights will work, also lights just don't show on some areas of terrain due to the light effect being under the ground, so try moving elsewhere. If neither of those help please try again with an unmodded install -
Crash on entering VAB/SPH
sal_vager replied to Zinq's topic in KSP1 Technical Support (PC, unmodded installs)
Okay that's weird, so it says Nvidia in your logs now? Try deleting the settings.cfg so KSP uses the defaults, and use the KSP.exe instead of the launcher, also add KSP to your antivirus trusted list. Upload the log from that please. -
Crash on entering VAB/SPH
sal_vager replied to Zinq's topic in KSP1 Technical Support (PC, unmodded installs)
Hi Zinq, something's not right as KSP is not using your Nvidia 740M, it's using the Intel gpu. Depending on your laptop there will be a physical switch for the graphics card, a keyboard combination or it'll be en/disabled via software. You may also find an option to run KSP with the Nvidia when right clicking on the exe file. -
Windows 10 issue
sal_vager replied to Vegatoxi's topic in KSP1 Technical Support (PC, unmodded installs)
Don't force openGL on Windows 10, it's unreliable, especially if you have dual monitors. Delete your settings.cfg and start KSP normally please, also make sure your graphics drivers are up to date. -
Windows 10 issue
sal_vager replied to Vegatoxi's topic in KSP1 Technical Support (PC, unmodded installs)
I don't know, I assumed if you had bCrypt installed you'd know it was there. You could test running KSP from a memory stick as that wouldn't (shouldn't?) be encrypted. -
Windows 10 issue
sal_vager replied to Vegatoxi's topic in KSP1 Technical Support (PC, unmodded installs)
Are you running KSP from an encrypted drive? I see bcryptPrimitives.dll in the log, that's probably not a good idea. -
Well, all I do is put a strut from the other end of my payload to the bay wall, usually one single strut is enough and as it's in the bay it isn't adding to drag. That's only good for taking cargo up though, as you can't place struts in space. So what I do when I have an object I know I want to recover later is place docking ports on both ends, small ones are fine. Something I need to test is using landing legs to hold the floppy end of a payload, the feet of some of the landing legs are actually separate parts, so they can press against parts of the same vessel. Wheels are also separate parts, so a small wheel in the floor of the bay should act as a stop, preventing the payload from moving through it. Edit: Works with the LV05 and LV-01 if the wheels are placed on another part outside the bay then clipped inward, doesn't work if placed on the bay itself. Yep that's a full orange tank, it's still supported even if the bay is closed and reopened.
-
Windows 10 issue
sal_vager replied to Vegatoxi's topic in KSP1 Technical Support (PC, unmodded installs)
Vegatoxi, please see [here] and upload your output_log.txt and dxdiag. Without those everyone is just guessing. -
I have seen this before. It was causing KSP to crash for another member, any software that is touted as being able to "boost" gaming generally doesn't do much more than look fancy and cause instability, and many of the Steam reviews for this software say it's junk. Disable it and try KSP again. It's probably just chewing up your RAM, the error log says you got up to 69% of your 4gigs, KSP is a 32bit application so can only access about 3.5gigs maximum, if other programs are using that RAM there's less available for KSP to address.
-
Graphic problem on new iMac
sal_vager replied to VOXsp's topic in KSP1 Technical Support (PC, unmodded installs)
Were you on the Minmus flats? It might not show the effect to the same extreme as the Minmus slopes, and I think the flats are just a sphere mesh anyway, not generated at all. As for the crash, no idea, not from an OSX crash log anyway, there should be a crash folder containing several files and with the date of the crash in the KSP folder if KSP was able to write one. If it is not there then the player.log from immediately after the crash would be needed, but if KSP was re-started it will have been overwritten. -
The Linux Thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
Er, no, I think you need to re-read this issue, the drive is there but it's being detected as a cdrom, not a hdd, so it cannot be selected as an installation target. The dvd drive with the linux cd is another drive entirely from the one causing this issue. -
No heat effects on re entry
sal_vager replied to John FX's topic in KSP1 Technical Support (PC, modded installs)
This is not an unusual thing for software to do though, I have plenty of games that will not find their own data files if you run them from some other working directory, they expect the files to be on paths relative to the .exe What the likes of ckan and Jebretary need to do is change to the folder that the user has specified that KSP is in, then run the .exe so the relative paths aren't broken. Steam already does this, as do most shortcuts created by an installer, they add the path to the folder of the target executable so this issue is not noticed for most games. But user made shortcuts or those made by 3rd party programs don't always do this, which results in "bugs" when data files cannot be found. KSP's file handling is working, just don't break it. -
Not from Squad, no, but nearly all the versions from 0.13.3 and earlier are available and free to share.
-
The Name Change Thread (WARNING! ONE TIME ONLY!)
sal_vager replied to Souper's topic in Kerbal Network
Sure thing Atryaz_25609 and WinkAllKerb'' Don't forget to log in with your new name. -
The Linux Thread!
sal_vager replied to sal_vager's topic in KSP1 Technical Support (PC, unmodded installs)
This may be the wrong track, but it's possible the drive is damaged. This post shows a person having a similar issue but with a Toshiba HDD, which turned out to have many damaged sectors when scanned with chkdsk. I find very few results when searching for this kind of problem which suggests that it is uncommon, I'd expect most HDD's with damage to either be more obviously damaged, or not work at all. If the drive is old and well used that might account for it, and doing a surface scan of the drive to check it is okay before continuing might be a good idea.