stoppingby4now

A portion of usable VRAM will be mapped into the process address space in Direct3D applications, so yes it will count. But you won't end up with the full amount of VRAM being mapped. This article is a great read in general in regards to memory handling in Windows. Page three gives more information on how VRAM mapping into the process space has changed (included in the spoiler below).

What about Win NT, Win2k, server 2003, etc? Those weren't stable? Lot of servers and enterprise machines ran on those back in the day. Not sure about vista/win7 to be honest so I won't comment there. I meant consumer systems, Microsoft servers/workstations are actually quite good until you compare them to Linux. I think it really comes down to who is administrating the system. There is no comparison between Windows servers and solid UNIX servers (I don't consider Linux desktop distributions to count). The former requires significantly more attention and maintenance to keep stable, is more complex to secure, and suffer from far more downtime (some of which is inherit to the patching process, but by no means is the primary culprit).

I tried to add a comment to my mod, and it apparently timed out, meanwhile removing the textbox where I had added the comment. After a refresh to verify if it had been added or not, I then get the message that the mod has been hidden by the author. They definitely have a lot of problems going on right now, both in performance, and code logic. The latter is much worse than it has been in the past in my experience.

Gotta love the Nexus. Fatal error: Call to a member function SetLocal() on a non-object

I've always had issues with the Nexus, primarily between 1am and 9am MST (which is pretty much the main portion of the day in the UK). A lot of 500 errors, and very low response times when I actually could get a page to refresh. Sometimes I will experience it during late afternoon/early evening here, but it's not often.

Here is an image of Curiosity descending with the parachute open, caught by the Mars Reconnaissance Orbiter Satellite.

Great video. [video=youtube]

Awesome!

It truly is amazing that the landing went off without a hitch. A very technical landing, planned from a completely different planet. I'm so pumped right now. :D

Curiosity has landed on Mars using a "Sky Crane". Very amazing. https://www.nasa.gov/externalflash/mars/curiosity_news3.html for you late nighters.

From my viewpoint, it seems that the willingness to communicate is inversely proportional to the number of industry investors involved. It's sad, but they hold the puppet strings. If they see/hear information they don't like (regardless if their belief holds any weight), they sell sell sell. I applaud the influx of indie games and private developers, and hope that they can help to shift this flawed mindset. But, that also doesn't mean that everything is directly related to that. In some cases, you don't want to share information when new technologies or game breaking developments are involved. You don't want to help your competition become a direct competitor too quickly.

I read the discussion that unfolded, and to be honest all I see is a lot of accusations which may or may not have any validity. If the parties involved wish to continue down that road, it will be something for the Nexus staff to deal with. We will not tolerate the nature of that conversation bleeding over here though. Edited.

It's not showing up in Steam's app list via their web api. Wonder if they just haven't updated that yet.

It recognized the CK as v1.6 even though I had it uninstalled o.0 With the CK it took ~45 seconds to enable/disable and without it about 20 seconds for both as well. And of course, Bethesda hasn't skipped a beat. 1.7 has been released, and in my testing last night, I had accidentally left my automatic updates on enabled and got it. :facepalm:Lol! Â I let myself get it, but I have a 1.6 backup if you'd like.I'm good, I just recovered from a restore point. I forgot to also inquire about what you are using for storage? I'm assuming HDD, but am curious at what rotation speed, and RAID if any.

It recognized the CK as v1.6 even though I had it uninstalled o.0 With the CK it took ~45 seconds to enable/disable and without it about 20 seconds for both as well. I had that happen in one of my test cases. I uninstalled CK with automatic updates still disabled. In that case the files still exist because the file permissions prevent their deletion, but the registry key is gone. If you then try to install the CK, the uninstall registry information gets created even though it can't download anything. There may be another scenario as well as to why the registry key for uninstall information would still be there. And of course, Bethesda hasn't skipped a beat. 1.7 has been released, and in my testing last night, I had accidentally left my automatic updates on enabled and got it. :facepalm:

I'm using recursion in the file permission functions for directories, which is the only thing I can think of code wise that could be causing an issue. I could remove the recursion and just add in the extra logic and see if that helps in your case. That's still quite a drastic difference from what I'm experiencing. EDIT: Try this build and see if the times improve.

[video=youtube]www.youtube.com/watch?v=NHyGzKCS4XY

Wow, 30 seconds? Latest build for me is taking about 3 or 4 seconds with CK installed (practically instantaneous without it). Will be interested in hearing how long it takes for others.

Current beta version 1.5b available for testing here. This also locks down the CK if it is installed. Since I haven't taken the time to become familiar with the CK, I need feedback from those that are to know if there are any issues. Version information for each of the products is also displayed if the application is determined to be installed. Since there are a lot more files that get locked down (when the CK is installed), it can take a second or so for the status to update. For now, I just disable the enable and disable buttons until the process is complete. This does require that the uninstall registry keys exist for the apps. The location of these keys are below. 32-bit HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 72850 (Skyrim) HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 202480 (Creation Kit) 64-bit HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 72850 (Skyrim) HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 202480 (Creation Kit)

Since the CK isn't very big, could you try deleting local content for it only so that it truly uninstalls it, then re-install normally? That would at least narrow down if it's a post install cause or not.

Installed Win8-32, Steam, then the Creation Kit. I get the expected registry key: HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Steam App 202480 Odd thing is that with SkyrimInstallTest I'm getting the unhandled exception in Win8 as well (but not in Win7). But if I run my latest build of SU in Win8, it detects CK via the above registry key just fine and identifies the state of Automatic Updates correctly. No idea why you aren't getting the keys. They should exist, and are going to be required in order for SU to work properly going forward. Would be nice to be able to track down what is causing the discrepancy on your system.

Downloading win8-32 to install in a VM to aid in tracking this down. Though for short term (at least next release of SU), I may end up having to say that Win8 is not supported until I can figure out how to get at that uninstall information.

Can you search with Data and Values filters in the Uninstall path for 72850, and also "Creation Kit".

Did you manually check HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall? Does that path even exist? Also forgot to mention that only "keys" should be checked for search options when searching for "Steam App 72850". The above should not have returned in the search. I'm now fearing that Win8 has completely changed where its uninstall information is stored. Without that information, the end goal of SU is a bust on Win8.

Updated that app with a couple tweaks (same download location). Not sure if it will "fix" the win8/32bit lookup, and pretty much doubt it, but trying things in small steps.