Jump to content

diamond-optic

Members
  • Posts

    11
  • Joined

  • Last visited

Reputation

2 Neutral

Contact Methods

Profile Information

  • Location
    NY, USA

Recent Profile Visitors

799 profile views
  1. Sorry if this actually isnt related to BDB (probably isnt lol).. But does anyone else have issues with the centaur upper stage tank when using conformal decals on it? (note: this does NOT happen without the decals present). Whenever I jettison the tank insulation my log file is getting slammed with a repeating error. It results in the log becoming 100's of mb's pretty quickly and then a short while later the game gets incredibly laggy as a result and will eventually crash. It seems if I jettison the insulation in the atmosphere, the errors appear to start imediately, where as there seems to be a delay if I do it while already in orbit. If i jettison the insulation on the pad, no errors till after I launch and reach maybe around 1000 meters up. I'm trying to remove a few mods each time I restart the game to try and narrow down some more specifics with it so maybe I can isolate some sort of mod conflict or at the very least get the log to a more manageable size, but it is taking forever via trial and error because of the load times and the log size etc. Obviously I can't even say for sure what the root cause is just yet, but it only happens if I have conformal decals on the part and the error lines that are repeated 1000's of times in the log mention conformal decals so I assume theres a connection between them and this error (maybe i need to ask in the conformal decals thread instead?). Just wondering if maybe anyone would have some ideas that could make troubleshooting this a bit more efficient. Also seems if I save the game after this starts happening and then reload the save, the error stops. Could it just be an issue with attaching the decals to a jettisonable section of a part? I have no issue with the atlas booster stage that also has decals on it, and no issues with any saturn stages that I have decals on them.. But if it was just an issue with decals on jettisonable parts I would think that I would have found someone else here having this issue because there is no way I'm the only person who has put 'united states' down the side of their atlas-centaur rocket lol. I know this isn't probably useful at all without the entire logfile but this is what is repeated 1000s of times in the log. Uploading and posting a 500+ mb log file seems excessive at the current moment and I'm just hoping maybe someone might be able to say 'try this..' or 'remove mod XXXX...' etc: starting to think I need to do a completely fresh reinstall sooner than later just to clean out all the mod stuff of my current install.
  2. I think i might have solved the AA problem. Can you test on your end with this file (..\GameData\TUFX\Plugins\ - backup the original too): https://github.com/diamond-optic/TUFX/raw/AA_Scene_Change_BUILDTEST/GameData/TUFX/Plugins/TUFX.dll *edit* To explain what I changed... There was this part of the code: onAntiAliasingSelected(tufxProfile.AntiAliasing, false); layer = activeCam.gameObject.AddOrGetComponent<PostProcessLayer>(); layer.Init(Resources); layer.volumeLayer = ~0;//everything //TODO -- fix layer assignment... Log.debug("Layer: " + layer?.GetHashCode()); which I think basically means it was trying to set the AA mode before it set the layer variable. Hence why it was giving a 'layer = null' error. Moving the onAntiAliasingSelected() below the layer = activeCam.... line seems to have fixed it for me
  3. Yeah in the long run that would be a better option for sure, the sliders aren't super accurate (not that it really matters much in this case) and they are a bit clumsy... but the code was already there so it was the easiest. Besides that is well beyond the scope of my knowledge right now. I tried to stay away from any coding the last couple of games I've been playing because its a rabbit hole that results in never having time to actually play (and seeing how many things here have your name on them, I assume you might know that too lol). But im too enamored with ksp so who knows now, and it has a rich modding community on top of that :-D
  4. Idk, because a hard-coded value is yucky? lol :-P ...because the inconvenience of having to change it after any update? But I can just keep a fork going for myself if you disagree.
  5. Yup, same thing with scene changes for me. Doesn't matter what profile, which AA mode, or if hdr is on or off etc. Took me a while to realize it was from each scene change.
  6. If using Critical Temperature Gauge docked to the altimeter (where it looks best), the hud display from this gets partially covered up. ..And honestly I'm fine with modifying it for my own use if necessary since this may not be an issue for most. And if so, a real quick glimpse looks like I could maybe just modify the ybase in WaypointFlightRenderer.cs before it runs through the different hud displays? * edit - 09-17-21 * I ended up adding an option to override the hud position and sliders to control the x/y values to the settings popup. I'll submit a pull request once I finish some extra testing on it. https://github.com/diamond-optic/WaypointManager/tree/HUD_Position_Override
  7. Ahh gotcha. I appreciate the input. If i need to choose between KSP-AVC and Craft Manager.. easy choice as I dont think I could stand not using craft manager anymore lol
  8. Ok, sorry about that. It's still happening with 1.1.1.1 for me. I did some quick testing and for me it seems to be KSP-AVC and Craft Manager. If i disabled either one (and leave the other enabled) it seems to load fine. Leave them both enabled and it doesnt load. Here is the logs from those 3 scenarios: https://drive.google.com/file/d/1OzSeSlCcCQiYxkwdK8fMz6Tf6612PQLS/view?usp=sharing Not sure if that helps any or if I'm just plain wrong about that combo being the issue, but I honestly can do without KSP-AVC and I probably won't be reinstalling it anyway once I get enough time to do a clean install. Yeah I just noticed that too.. I am overdue for a fresh install and dumping all the mods I dont use/need anymore so that probably needs to be done sooner than later.
  9. I'm getting the same thing with 1.1.1 ..stuck on loading screen without loading progressing Log: https://drive.google.com/file/d/1Mdzi_wxrN19Faimqw8j2mdKK7A_845V3/view?usp=sharing
×
×
  • Create New...