43 réponses à ce sujet

[kevL]

i'm on XP ... i miss the 2000 look :\

[unclejoe1917]

That's my point; I have Windows 8.1 and the layout and aesthetics are the same classic ones I had when I had 7. I wouldn't like it otherwise either.

I'm going to have to look into what you were talking about then.  If not for the app screen and the bullshit that pops out of the sides of the screen, i could be okay with 8. 

[Arkalezth]

It already came installed when I bought the computer, but it looks like the one I have is "Classic Shell", if you want to check it out. I -think- that's enough to get rid of those things you mention and have the classic look.

[GCoyote]

It already came installed when I bought the computer, but it looks like the one I have is "Classic Shell", if you want to check it out. I -think- that's enough to get rid of those things you mention and have the classic look.

 

My wife got a laptop with Win 8.0 and hated it until I installed Classic Shell. Now at 8.1 she merely tolerates it until we get something better.

[husveltarn]

Just installed windows 10 and i can run the game without issue so far. Only thing i had to do was go into the nwn2 install dir and run the dx9c setup in utils. 

[Kanis-Greataxe]

May just have to give Win 10 a shot on one of my machines (most are running win 7) I have one I'm getting ready to redo anyways so may just try it with that one. can always go back if I don't like it.

[Thorsson64]

For me it looks/acts very similar to 8.1 at the moment.

[bealzebub]

The game seems to run fine, but the toolset is not showing any graphics. It loads fine and stable, but if I open an area or create a new one, the window stays blank. The same goes for the preview window, if I select a creature or placeable, it remains blank.

I tried running it on different compatibility modes, reinstalled dx9, and reinstalled .NET Framework. 

[bealzebub]

I figured it out. under the compatibility settings, a box for "Disable display scaling on high DPI settings" is pre-checked. I un-checked it, and everything seems ok.

 

I also noticed that the appearance wizard is fixed, as well as refreshing change issues I was having.

[Groove Widdit]

The reason Microsoft devs have given for skipping "Windows 9" is because there's software out there that was written 10+ years back when win95/98 were still relevant. These applications would for example need to do one thing on Win95/98 and another on WinNT. The simplest solution was naturally to do something like this:

String osName = System.getProperty("os.name");
if(osName.startsWith("Windows 9"))
	os = new Windows9x();
else if(osName.startsWith("Windows"))
	os = new WindowsNT();

It's a clumsy hack of a solution, but did work perfectly. Right up until you'd want this to run on something called "Windows 9".
This may seem silly and a non-issue: After all who'd still use ancient software like that? Well you'd be surprised. A lot of companies and other institutions still use software that's decades old. Why change it if it still works, right? And even software that's "new" often still contains old code. Why throw away everything and start from scratch when you don't have to, right?
So it's plausible that this was one of the main reasons why they skipped "Windows 9", since that would again be the simplest solution.

Everything about Microsoft is a clumsy hack.

 

[drechner]

I get that it's "cool" to hate on Microsoft, but the reason "Windows 9" doesn't exist has absolutely nothing to do with them, but rather lazy software engineers that couldn't be bothered to actually read the Windows UID. Meaning, Microsoft is actually going out of their way to ensure software doesn't break because a large number of coders couldn't be bothered to actually use the correct reference; that's pretty nice.

[rjshae]

[drechner]

Just an update: I upgraded to Windows 10 from 8.1 and everything works great so far. Absolutely no issues with the editor or the game (or any others for that matter)

[Lance Botelle]

Just an update: I upgraded to Windows 10 from 8.1 and everything works great so far. Absolutely no issues with the editor or the game (or any others for that matter)

That's good to hear ... I may try the upgrade in the near future then ...

Cheers,
Lance.

[Shallina]

I upgraded from 7 to 10, no issue everything worked perfectly, and still does.

[Thorsson64]

From what I've seen 10 is no problems if you've been a good boy (/girl). If you have all sorts of crap in your registry though (like my younger brother had...) then it could all go completely ****** up (if you'll pardon the expression).

[Lance Botelle]

Hi All,

Well, I did try "upgrading" to Windows 10 on a couple of systems ... I am now in the process of returning to the original versions.

NB: I cannot say the new OS had any negative impact on NWN, but I can say that I simply did not like its effect on a number of other applications I had on the computers. From application compatibility issues, to general system notification "differences" and "failures".

Thankfully, I did *not* test this on my main NWN2 modding PC. (I just hope the other PCs restore OK.)

Cheers,
Lance.

[liorbil]

Running on Windows 10 here. The toolset doesn't work at all, in all the various compatibility modes. The game was a bit unstable, now it is better after a driver update.

 

Edit: Issue solved. Need to enable/Install .Net Framework 3.5 before installing the game.

[Kaldor Silverwand]

I was able to install the GOG version on a MacBook Pro running Windows 10 with Bootcamp. I was able to get both the game and the toolset working although I did have some trouble with screen resolution due to the MacBook Retina display.