• Content Count

  • Joined

  • Last visited

Community Reputation

699 Excellent

About diomedea

  • Rank
    Maxed entropy

Profile Information

  • Location where light is no more
  • Interests astronomy, cosmology, advanced physics and more ...

Recent Profile Visitors

4,962 profile views
  1. diomedea

    Guess Who Will Reply Next?

    ops, you got me! maybe, is @Deddly around too ?
  2. diomedea

    1.3 crashes more

    ok, thanks for that latest log. It still shows the pagefile being = 0 MB, though I'm sure you noticed. Actually, pagefile serves to allow RAM be swapped between applications, without that any other process loaded (even if currently inactive) stays resident in RAM and can't be swapped out. Meaning, the effective RAM available for KSP to run is even less (indeed, was reported as 725 MB free with that last error.log). With a pagefile large enough, OS swaps RAM content of inactive processes to disk, so to let all RAM available to the process in foreground. Am I right your system is Windows7 32bit? 32bit OS can only map up to 4GB memory with any application; however the low 2GB of RAM are by default to the system itself. Is possible to change how the system reserves RAM by use of 4GT and /userva system settings (info here). Glad you see launching in OpenGL works, indeed that mode takes less RAM. But if you observe the amount of RAM used by KSP (e.g., from a Task Manager reading) you'll notice to be quite close to the limit; anything like a complex game or add-ons will push over that. Indeed, before KSP_x64 was stable, I also had to use OpenGL with the 32bit versions of the game (plus some add-ons to reduce textures size, now no more required as KSP changed the format of those files to be smaller).
  3. diomedea

    1.3 crashes more

    Could you please show a new error.log after having set the pagefile? Previously was reported the OS had allocated only 2GB address space to the application, and KSP really can't work with that low amount of memory. I hoped the pagefile could allow the address space be increased, would like to see if the issue is still that or a new one.
  4. diomedea

    KSP Acquired by Take-Two Interactive

    Someone feels not able to speak freely here...
  5. Falling through ground is the result of missing or wrong colliders with the model of the part (same would be for moving through other vessels). If the tanks fall bottom-first, would be a collider for the bottom missing or oriented improperly. This could be an issue specific with the Procedural tanks add-on, if confirmed with only that add-on installed on a stock KSP install (plus all required dependencies for Procedural tanks to work properly, of course). In that case, better to report in the proper thread for it.
  6. Please provide us something to look at (what listed in this guide would fit for starters).
  7. Happy the workaround worked for you Thanks for DXDiag.info, interestingly in Diagnostics section it also reports a problem with KSP_x64.exe. However I'm not able to find hints in there showing the real cause, sorry. Believe at this point the cause be tied to that d3d9.dll, though it seems fine to me. Should you have other games using DirectX 9, those also may encounter issues (not necessarily all, sometimes a copy of that dll is installed with a game folder so to not depend on the one in system).
  8. diomedea

    KSP Acquired by Take-Two Interactive

    Yes, I was allowing myself a bit of humour. But you did well to alert me about the mood, sometimes I lose the meaning in such messages
  9. diomedea

    KSP Acquired by Take-Two Interactive

    Believe that won't happen. Squad still has a partnership about KSPEDU, a spin-off devoted to schools. That one can't be rated 18+ anytime and I'm sure Squad will honor that agreement making sure the base game doesn't either.
  10. diomedea

    Atmospheric Efficiency/optimal ascent speeds in 1.0?

    Thread is too old, the issue has changed with all revisions of atmo drag and thermal effects in KSP since then. Should a similar question arise with a current version of KSP, users should open a new thread instead. Locked.
  11. diomedea

    Kerbal crashes every 5 mins

    Glad to know you solved it, thanks for sharing the cause. From now on, will have to insist to get info about BIOS and overclock settings too when it is a system issue, instead of just one with KSP.
  12. diomedea

    KSP Acquired by Take-Two Interactive

    What about Squad services (this forum in particular with all the content from community members) ? Will these still be Squad property or transferred under T2? In which case, rules will change to suit the new property (hint) ?
  13. diomedea

    KSP Acquired by Take-Two Interactive

    Thanks for that, it's all I need to feel better.
  14. diomedea

    KSP Acquired by Take-Two Interactive

    @UomoCapra: a partnership with a renowned, experienced operator in the game industry like T2 is certainly a positive step, it ensures more funding for future development and (maybe) even plans for a sequel. Don't know of many other indie developers who stayed on their own for 6+ years with a product able to sell as much as KSP, Squad showed to be really committed to the game and community doing so. But now, should we expect another change in the EULA? even worse, will the DRM policy change and make our digital lives with KSP somewhat harder? Perhaps early to say, but this is my main concern with these news.
  15. The error.log shows "d3d9.dll caused an Access Violation (0xc0000005)" instead of a KSP or Unity file. d3d9.dll is Windows library for DirectX, isn't known for causing such errors (and your dll version seems fine). Also the nVidia driver (nvldumdx.dll, though having been reported in connection to various issues, has never emerged to be the cause. So, can't find any evident cause just now. Would you like doing a couple tests to better define the issue? 1. Launch KSP in DX11 and/or OpenGL mode instead of DX9. Doable by adding " -force-d3d11 " or " -force-glcore " as arguments; with Steam, open Properties for KSP, General tab, Launch settings to paste the argument. If the issue was really caused by d3d9.dll, there shouldn't be an issue in these modes. 2. Save a copy of your settings.cfg file somewhere safe, then use a text editor to open the file within KSP root directory. Search for lines with "SCREEN_RESOLUTION_WIDTH = " and "SCREEN_RESOLUTION_HEIGHT = ", those hold the current resolution settings. Change those to any valid combination supported by your display. Please make sure to use a combination supported. The display control panel should show which are valid combinations, those should be the same available in KSP settings. Should test 2. work successfully, please verify what KSP settings show for valid resolutions, it is expected those to match with the display control panel. If none of the above works, further info could be of help. Mind providing output from DXDiag?