-
Posts
195 -
Joined
-
Last visited
Reputation
43 ExcellentContact Methods
- Website URL
Profile Information
-
About me
komrade kosmonaut
Recent Profile Visitors
3,972 profile views
-
[1.1.x] CoolRockets! Cryo and Launch Particle FX
speedwaystar replied to sarbian's topic in KSP1 Mod Development
CoolRockets/Smokescreen effects are working fine on the launchpad, but in the VAB the "show in editor" buttons do nothing, and if debug=true, the editable values appear in the properties menu but the sliders don't work. -
PartTools 1.1 - new shaders?
speedwaystar replied to Dr. Jet's topic in KSP1 Modelling and Texturing Discussion
looks like it's gone in 1.1.2 parttools, so i suppose that answers my question! -
PartTools 1.1 - new shaders?
speedwaystar replied to Dr. Jet's topic in KSP1 Modelling and Texturing Discussion
standard_bumped looks pretty nice in Unity (but doesn't make it through PartTools yet). any update on when it might be enabled? -
about a billion of these errors in ksp.log: [EXC 17:24:33.477] NullReferenceException: Object reference not set to an instance of an object KRASH.Hyperedit.OrbitEditor.Simple (.OrbitDriver currentlyEditing, Double altitude, .CelestialBody body) KRASH.SimulationPauseMenu.DrawGUI () KRASH.SimulationPauseMenu.OnGUI () [EXC 17:24:33.526] NullReferenceException: Object reference not set to an instance of an object KSP.UI.Screens.AltimeterSliderButtons.LateUpdate ()
-
[1.11] RemoteTech v1.9.9 [2020-12-19]
speedwaystar replied to tomek.piotrowski's topic in KSP1 Mod Releases
it's up to ShotgunNinja to tell RemoteTech to disable communication for the duration of his blackout. it's not RemoteTech's job, nor is it possible since RT has no way of telling when another mod has decided that a coronal ejection is occurring unless that mod tells it. Luckily, RemoteTech provides a software API for other mods to easily do this. for instance, Kerbalism (or any other mod) could set RemoteTech.API.HasAnyConnection for the vessel to false, and RemoteTech would dutifully disable the vessel's communication channel; then set it to true again after the blackout has run its course. -
it was working normally before the update which added the choice of two dependencies. until the problem gets fixed, you can simply tell CKAN to uninstall scatterer, then reinstall it. a clean install doesn't throw the error, only an upgrade to an existing install. EDIT: just noticed @Steveo has already posted this workaround.
-
many thanks. since i accepted the R-1V and V-2N20 at the same time, would this have anything to do with it? CONTRACT_FINISHED { guid = 56bbe9a4-8bd1-4ad6-976c-e5106022de69 <snip> subtype = R-1V title = R-1V <snip> REQUIREMENT <snip> PARAM { <snip> PARAM { name = IsNotVessel id = IsNotVessel state = Complete disableOnStateChange = False values = ,,,, ContractIdentifier = HistoricMissions.R-1V title = Must be a new vessel upon accepting this contract. notes = completedMessage = fakeFailures = True allowStateReset = True failWhenUnmet = True vesselKey = V-2N20 // <---- was active at the same time, or possibly before, because i also accepted the blossom-1 mission <snip> persistent.sls is here.
-
@Whitecat106: sorry to pester but further to my sequential missions question above, i'm now all the way up to the early Pioneer Program and have been offered only US missions in a steady stream, one after another. the Soviet mission tree is stalled at R-1V (which I completed), never offering me R-2A or later. is this expected behaviour?