smjjames

Did you see whether there was a 'memory leak' (whether or not that's the correct term to be applied here) happening with it because GCmonitor showed a small, but steady, increase in memory usage over time. Without Better Burn Time, it didn't happen.

I wasn't even using Blizzy's Toolbar when I checked, but if he removed the toolbar button temporarily, okay. Didn't realize he did.

Really? This question comes up every version, even minor ones, heh. I'd say both because they complement each other.

Yeah, I did a test for sure later and the button really isn't showing up in any scene, 32 and 64bit. I was able to change the font size so that it wasn't quite so big (20 down from 30) in the config, so the lack of a button not a major issue for me. Output log: http://sta.sh/02cqxibfzr2v

Continuing the discussion from over in the Contract Configurator thread, I removed the ones without parameters and it stopped giving the error now,

Oh right, sorry. Well, it's an older save transferred into 1.1, so it could easily be that. Also, it seems to be largely the anomaly contracts that are spazzing out, I'll continue the discussion in the DMOS thread though.

In an old science mode (where Strategia shouldn't even be active) save that I transferred to 1.1, I'm getting a spam of this error when I research a tech: NullReferenceException: Object reference not set to an instance of an object at Strategia.CurrencyPopup.OnGUI () [0x00000] in <filename unknown>:0 It does stop, it just produces a lot of them for each instance. I haven't tested it out in a new save though, and I'm using CTT.

Hey @nightingale I'm getting loads of NREs and some other exceptions coming from the DMagic anomaly contracts. I'm not totally sure if they are coming from CC or something else. This is when loading an old 1.0.5 save that was transferred to 1.1. Output log: http://sta.sh/0alf0a59d3 persistent file from that save: http://sta.sh/01pavwb7coa9

Same here, I like having it so that I can see the exceptions and errors that come up (most of them anyway).

Okay. I just wanted to confirm if other people were having the same issue or if it was just me somehow. edit: Turns out the button isn't showing up at all, and neither is the one for the makeitsmaller mod. I'll have to investigate a bit later.

I know, but it's not even showing up in Blizzy's Toolbar either. I'm doing a sort of final kickoff for my old saves, so, I'm not doing any serious bugchecking atm.

Is anybody else having problems with the button not showing up for blizzy's toolbar?

Just came over here to report that one. Still happens in 1.1 full and happens on scene change in general maybe, when switching from flight to VAB or launching from VAB/SPH. edit: I think this might be contributing to a maybe memory leak or a general increase in memory usage, not sure....

*grabs the alpha versions for the fun of it* Well, it's a final kickoff for my old saves.

I was on the pre-release beta, I know about the issues with the legs and wheels Thanks though.

IR 2.0 includes all the Model Rework stuff, right?

Heh, just in time. I'm gathering up mods to update into my soon-to-be-1.1 old saves.

Maybe someone can take up this mod for Tiberion? I'm pretty sure it's a popular mod. Shouldn't have too many issues though.

If you look at his profile, he was on two hours ago, so he's around. Not active doesn't neccesarily mean they aren't visiting from time to time.

I have a bunch of ships using that in my soon-to-be-transferred-to-1.1 saves and I really like this mod. I know @Randazzo closed his old threads saying that he was removing them for a refresh, but he never did make a new thread for that or his other stuff, and now 1.1 is here. so.... I'm just wondering what's going to happen with that one.

Agreed here, I was slightly puzzled for a second when I saw the un-updated title despite downloading the update for 1.1

@DMagic TYVM for fixing the bug with resetting micro goo and mat bay parts! I haven't given them a look myself though.

It also doesn't like being in windowed mode I think, for some reason. Using borderless windowed fullscreen by way of -popupwindow has the settings screen work.

The tl;dr answer to that is: The wheels are deceptively complex and turned out to be more complex than the devs thought they were. But hey, I too wish they would have taken another week to try and sort things out better, but that's not what happened.

You probably wouldn't be able to go fast enough in a rover to achieve the same camera effect. At least on wheels only.