![]() ![]() This is just to provide insight into our progress on the most concerning issues to our community. Note: this report is not fully representative of the work our team is focused on. Known issue, investigating solutions for this and other pause-related issues Investigating, might be caused by old savesĬannot create/edit a maneuver node when game is paused Landing gear blocked when it is not Īlmost all of the Navball stuff disappears ![]() SAS does not hold orientation during time warpĬontrol Surface Oscillation in Atmosphere ![]() Struts: ctrl+z in the VAB renders struts/fuel lines invisible, visual bugĮlliptical Solar Orbits Cause Timewarp Under Acceleration to Stop Producing Thrust Timewarp under Acceleration stops Engaging Properly after a certain amount of years have passedĪcceleration During Time Warp Doesn’t Work at Times If a craft with landing legs is saved in low orbit, when reloaded the craft will experience massive force in the retrograde directionĮngine Plate Fairing Respawns after load or switching vessels On Undocking in Low Orbit, Landing Legs are Causing Massive Force to be Applied in a Retrograde Direction Even When RetractedĮxtended Landing Legs are Causing a Massive Kick in the Retrograde Direction when in Low Orbit After Disengaging Time Warp Surface Collision not even with Terrain Mesh ![]() Two separate issues, one with struts, one with symmetry. Moving a radially attached part with a strut on it, break the game Rovers are Hitting a Physics Glitch Every 1000m from the Location of Rover Being Loaded into the Game With Disastrous Resultsīlack visual artefacts when passing through cloud layer (AMD) Phantom forces when deploying landing legs/gear Unable to repeatedly reproduce, need more information Surface Rendering Fragment Shaders are Inefficient : We believe this requires some reevaluation by fans post v0.1.5 as we implemented mesh bucketing for terrain which should have significantly impacted the original issues.Ĭamera Resets Position Map View : Has been "upgraded" to this list as it and many other camera issues are planned to be addressed in future camera systems work, scheduled for post-For Science! Wobbly Rockets : Improvements have been fully implemented (see the video in the last update) and are ready to ship for For Science!Ĭalculating Physics of all parts of all Crafts : Improvements are fully implemented and are ready to ship for For Science! You can read more about the justification for that change in the last update, but one of the things we did commit to was to provide insight on the issues that we remove from the list when we have notable updates. Last week we shared a major change to the K.E.R.B.: removing entries that require fundamental feature overhauls. As always, thank you so much for reporting and upvoting bugs - it truly helps the future development of KSP2 v0.1.5 has been out for two weeks and we've seen so much more engagement with the K.E.R.B. update, we have somewhat of a shorter post today. RenderDevice=OpenGLDrv.Heya Kerbonauts and welcome back to the K.E.R.B!Īfter the doozy of the last K.E.R.B. I have looked in my System Folder for Killing FLoor and found the Core.System info in the Default.ini file. I keep getting the "Could not spawn a GUI Controller!" Error each time I try to run Killing floor. The gameplay has not changed really though. PS: Be advised that the standalone KillingFloor as found on steam is really a huge upgrade compared to the original mod. I am pretty sure though that if UT2004 is running fine by itself, that this is causing your problem. Sorry I can't be more specific on file names etc., but I have no longer installed UT2004, let alone KillingFloor. You may have to rename it to the KF logo file name which should be there to make it work. Copy it to the Help subdirectory of the KF mod directory. This file is called UT2004Logo.bmp or something like that. This splash screen is just a bmp file, which I think is located in the Help subdirectory of your UT2004 installation directory. My solution was simply to replace the KF splash screen with the default UT2004 one. For some reason later UT2004 builds couldn't handle it anymore. If I remember correctly the cause was the special splash screen that comes with KillingFloor. Usually thats because of an error in an ini file.Ĭan you paste the contents of your ini file and your core.system?Īlso make sure your directx is is updated. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |