Jump to content

sal_vager

Moderator Emeritus
  • Posts

    17,670
  • Joined

  • Last visited

Everything posted by sal_vager

  1. Thanks Anth12, now I at least know what to ask others with crashes in flight :/
  2. If you'd like we could try fixing it up for you, can you post the craft file?
  3. This the first I've heard of them not working, sorry but I don't know if there's a way to change this, but Squad is working on adding other languages, hopefully Chinese is one of them.
  4. When you said you tried the demo do you mean the demo of KSP? It was made with an older version of Unity. In Steam you will find a betas tab in KSP's properties, you can select the last stable version from there, and maybe the last pre-release as well if it's still available.
  5. It has to be something in KSP then, does the last stable release on Steam work for you?
  6. Hi @lobe, we're definitely going to need info on this one.
  7. I really don't know, not without knowing how to get into this state, you both use AMD graphics which could be a factor. Can you give this a go?
  8. I just wish I had the right answer for you, as it seems to be crashing just as it switches to the main menu 3D scene it's possible that you need to check your graphics driver, though I don't know why KSP 32bit is working, you have a 64bit operating system so much be running 64bit hardware, so it should just work. Your driver is dated 24th of October, so is not old. Driver Date/Size: 24/10/2016 21:00:00, 1579136 bytes But there have been reports in the past of drivers being rolled back by Windows updates, so it's at least worth looking into reinstalling the driver. Hmm, this might be something, despite reinstalling, KSP is still trying to start with a resolution matching your screen, instead of 1280x720 as it would with a default settings.cfg desktop: 1920x1080 60Hz; virtual: 1920x1080 at 0,0 If it's still doing this with a deleted settings.cfg then it's possibly the Windows registry key at fault, as that's the only thing that would survive reinstalling. But editing the registry isn't trivial.
  9. Yeah, it's not helping sorry, do you have any other 64bit games and are they working?
  10. What's PCmeterV0.3 do? Some software that monitors memory, clock speed etc, can make KSP really unstable.
  11. Okay, RtlLookupFunctionEntry is a Unity engine error, but I can't see what might have caused it, does this crash happen frequently and can you recall what you did just prior?
  12. I see a lot of mods, any one of which might be causing an issue with your game, if KSP worked before on 64bit then please test a fresh unmodded install, make sure that is working first. Can I please have a new log from an unmodded install, thanks
  13. Okay that sounds more like a permissions issue, KSP isn't able to write the log if it doesn't have write access to the folder, and it will try to write a new log every time it starts. Can you please try copying the Kerbal Space Program folder from Steam to C:\Games\ and run the KSP.exe then the KSP_x64.exe from the copy, if it's a write permissions issue the copy will start.
  14. You should have a new output_log, it might show something new.
  15. It should open the dialogue to set a target now, double clicking was found to be unreliable.
  16. In your position I'd try deleting the settings.cfg as that can randomly fix things, @Cratos should as well, also what other software are you running?
  17. Maybe reinstall the Audigy driver and reboot, but I'm literally guessing here, I've not seen your issue before.
  18. Okay, based on your log @Cratos I think you're having an issue with your sound card driver, FMOD is used by the Unity engine to provide cross-platform sound and it's throwing continuous errors for you. Sound might be fine elsewhere but if FMOD isn't able to load properly neither will KSP, there was a similar issue on Linux not long ago where FMOD failed to load if PulseAudio wasn't running.
  19. Hmm okay, I thought you also had the FMOD error Cratos has but it's not there, @Cratos have you tried rebooting?
  20. I will still need the output_log, even if it does not show a stack trace.
  21. It's best to take a look here. The crash.dmp isn't actually very useful, there's never anything in it that leads to resolving an issue, the most important files are the KSP.log, output_log (in KSP_Data), your dxdiag hardware report and possibly a screenshot of your taskmanager processes. You can upload all these to a free dropbox account then post the share links here.
  22. It should make a log every time KSP starts, it's not dependent on KSP crashing, have you tried looking in C:\users ? It might be in a hidden application data folder which would happen if you didn't have write permissions for the folder where KSP is installed. That can occur when using a desktop shortcut, or starting KSP via ckan.
  23. Hi @xiaomin, do you mean when using Chinese characters?
  24. Hi @Starhawk it was changed to ` (backquote) so it doesn't conflict with the default Abort keybinding, also making it easier to use with tab and shift+tab to cycle planets.
×
×
  • Create New...