claclawolverine

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About claclawolverine

  • Rank
    Bottle Rocketeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i do have memgraph installed, as you can see from my mods list (second from the end) and i allocated 8 GB more to the game, but even so, the longer the game goes on, the more it stutters, even with more memory allocated. p.s. what does GC stand for?
  2. this is the link to my log
  3. https://drive.google.com/open?id=1e82_qjMz1kPjiawnxdz0kkS70GIEtMIl
  4. sorry XD i copied from dxdiag where do i find the log file? the game doesn't crash, so i don't have the error.log yes, i run it on a laptop, i tried to expand the allocated memory with memgraph and the situation improved drastically. now it isn't perfectly fluid but it doesn't stop every few seconds anymore. as i wrote, i tried to reinstall it from scratch, begin the game, move the camera around and see if it stuttered, then if not, install some mods and repeat. it went perfectly even when i finally reinstalled all the mods, but when i loaded my saved game it started stuttering again until the memgraph stuff that i mentioned before. it seemed that the problem was the advanced ksc in some way, i don't know. now i'm playing with the graphic options set to maximum performance through nvidia geforce experience, allocating 8 GB extra RAM via memgraph and it's playable. not perfect but fine.
  5. hi, i've tried every solution i've found on forums and posts everywhere i looked, but all of them seem to not work. i tried even to uninstall ksp (latest version, 1.3.1 64 bits) and reinstalling it, i tried to uninstall most of the mods, but the issue stays, it freezes for less time but still freezes, sometimes even every 2 seconds or so, in every part of the game (KSC, VAB, space, thrusting, not thrusting, reentry etc.). memory usage doesn't seem to be the cause of the problem, because with alt+F12 i can see that there are 1700 MB occupied while i have 16 GB RAM. i tried to modify the graphics configuration and it seems to have no effect whatsoever, both modifying the resolution or settings like anti-aliasing or v-sync, i tried even forcing the program to use opengl or setting the graphics from the nvidia panel following the guide provided by the community. i tried also to set the affinity of the processor to the game to prevent it from running on processor 0 but it had no effect. these are the specifics of my computer. Operating System: Windows 10 Home 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534) System Manufacturer: Notebook System Model: P65_P67RGRERA BIOS: 1.05.13 Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz Memory: 16384MB RAM DirectX Version: DirectX 12 Card name: NVIDIA GeForce GTX 970M Manufacturer: NVIDIA Chip type: GeForce GTX 970M DAC type: Integrated RAMDAC Display Memory: 11141 MB Dedicated Memory: 3038 MB Shared Memory: 8102 MB this is the list of mods i've installed. i installed them one by one with CKAN and there were no errors in installing or loading them from the module manager. all the mods are up to date today 17/01/2018 { "name": "TacAtomicClockIrradiated" }, { "name": "TACLS" }, { "name": "ModuleManager" }, { "name": "CommunityResourcePack" }, { "name": "BackgroundResources" }, { "name": "AtmosphereAutopilot" }, { "name": "WaypointManager" }, { "name": "AGExt" }, { "name": "xScience" }, { "name": "ConfigurableContainers-Core" }, { "name": "SolarScience" }, { "name": "SCANsat" }, { "name": "RealChute" }, { "name": "RealScaleBoosters" }, { "name": "SafeChute" }, { "name": "B9PartSwitch" }, { "name": "KerbalAtomics-NFECompatibility" }, { "name": "NearFutureConstruction" }, { "name": "NearFutureElectrical" }, { "name": "NearFutureElectrical-Core" }, { "name": "NearFutureLaunchVehicles" }, { "name": "DeployableEngines" }, { "name": "NearFuturePropulsion" }, { "name": "NearFutureSolar" }, { "name": "NearFutureSolar-Core" }, { "name": "CryoTanks" }, { "name": "CommunityTechTree" }, { "name": "AT-Utils" }, { "name": "CommunityCategoryKit" }, { "name": "ContractConfigurator" }, { "name": "Toolbar" }, { "name": "FirespitterCore" }, { "name": "GroundConstruction" }, { "name": "GroundConstruction-Core" }, { "name": "Konstruction" }, { "name": "RN-SPP" }, { "name": "UKS" }, { "name": "USI-ART" }, { "name": "USI-Core" }, { "name": "USI-EXP" }, { "name": "USITools" }, { "name": "Hangar" }, { "name": "HangerExtenderExtended" }, { "name": "Impact" }, { "name": "ContractConfigurator-FieldResearch" }, { "name": "ContractConfigurator-KerbinSpaceStation" }, { "name": "ContractConfigurator-Tourism" }, { "name": "Kerbalized-SpaceX" }, { "name": "DockSafe" }, { "name": "ExtraPlanetaryLaunchpads" }, { "name": "FinalFrontier" }, { "name": "HideEmptyTechNodes" }, { "name": "Karbonite" }, { "name": "KAS" }, { "name": "KEI" }, { "name": "KerbalInventorySystemNoFun" }, { "name": "KerbalJointReinforcement" }, { "name": "DMagicOrbitalScience" }, { "name": "InfernalRobotics" }, { "name": "TweakScale" }, { "name": "TooManyOrbits" }, { "name": "ToughLove" }, { "name": "Trajectories" }, { "name": "MechJebForAll" }, { "name": "NehemiahMultiPurposeParts" }, { "name": "NehemiahScienceCommon" }, { "name": "OrbitalMaterialScience" }, { "name": "NearFutureSpacecraft" }, { "name": "NearFutureProps" }, { "name": "KerbalAtomics" }, { "name": "DynamicBatteryStorage" }, { "name": "StateFundingContinued" }, { "name": "DeepFreeze" }, { "name": "EskandareHeavyIndustries" }, { "name": "HeatControl" }, { "name": "InterstellarFuelSwitch-Core" }, { "name": "KIS" }, { "name": "BetterBurnTime" }, { "name": "REPOSoftTech-Agencies" }, { "name": "RSSeaDragon" }, { "name": "SpaceXLegs" }, { "name": "SpaceY-Expanded" }, { "name": "SpaceY-Lifters" }, { "name": "CryoEngines" }, { "name": "StationScienceContinued" }, { "name": "USI-NuclearRockets" }, { "name": "LandingHeight" }, { "name": "NavballDockAlignIndCE" }, { "name": "KSPInterstellarExtended" }, { "name": "AmpYearPowerManager" }, { "name": "CactEyeCommunity" }, { "name": "ModularFlightIntegrator" }, { "name": "KerbalAlarmClock" }, { "name": "MemGraph" }, { "name": "CameraFocusChanger" } edit: i tried to uninstall the game, reinstall it and every time install a few mods and start the game to see if it would freeze in the ksc screen. to test it i tried to start a new game and move the camera constantly. i reinstalled all the mods without issues, so i loaded my save games again and tried to continue my game, and it started freezing again every few seconds. maybe the issue is the KSC in its most developed form? how can i fix this?
  6. i would like to use interstellar, near future technology pack and impossible innovations together in career mode, but there is a problem with the tech tree. is there a way to use all the three together (in career mode of course)? can i somehow mix the tech trees or is there a way to edit the tech tree of one of them to include the others?
  7. hi everybody, i've recently discovered some interesting mods that i would like to use simultaneously in career mode, and they are impossible innovations, interstellar and the various near future technologies. all of them have got a tree.cfg file and the last two have got a folder called treeloader with a treeloader.dll file in it. now if i overwrite this file i suppose that one of these mods won't work properly, while if i don't overwrite them one of them surely won't work. so, my question is: how can i use multiple mods with treeloader.dll and tree.cfg files toghether?? and when i've done how can i control that everything is ok? because i can't see if the treeloader will load correctly the last parts of the tree before unlocking them, and to unlock some of these features i could have to play for days. in sandbox mode it's everything ok but i suppose that it's ok just because it loads every part without looking at the tree tech(s). yesterday i saw that the tree.cfg files are pretty easy structured so i was wondering if i can modify a tree teck just by writing in the correct part of the tree.cfg the names of the new parts. for example can i copy and paste the names of the new tree nodes of, let's say, interstellar, in the tree.cfg file of near future tech? will it work? do i need also to move the parts in interstellar mod in the same folder of near future, or is it not necessary, or is it necessary to change the treeloader.dll file? for now i have tried to keep all the treeloaders in different folders (one with the original name, the other with a similar one), and i added just the tree.cfg file of near future, but the game sometimes crashes without a reason and without releasing a crash report (just stops working). do you have any idea on how can i solve this problem?