This likely should should go in the trouble shooting forum, but with the current traffic I figured I'd have a better chance here. Plus it is a toolset issue.
So I have recently returned to modding after a bit of time off. I have recently upgraded to a new computer and I suspect either it the OS or graphics card setting that are causing the issues.
What is happening is this:
-Area design: tinting and scaling to items in the area are usually not shown as they happen, instead I need to save and close the area and when it is re-opened all the changes are there. This happens 100% of the time when a second area is opened.
-Creature Design: Again tinting and armor changes aren't shown. I need to select a different blueprint then return to the one I am currently working on to see the changes. I have also run into an issue with one blueprint that would cause the toolset to crash when the basic tab was selected for the properties. It only seemed to happen with 1 blueprint, so I am inclided to write that one off as a fluke until it happens to at least another blueprint.
I have windows 8: I have the toolset to run in compatabilit mode -Windows XP (service pack 3) and I run it as an administrator.
For the graphics I have Nividia GeForce 660Ti.
I've searched around but haven't been able to find anything. So if you have a solution or some things for me to try let me know.
Thanks, Shaughn
having a few issues with the toolset
Débuté par
Shaughn78
, sept. 22 2013 07:11
Retour en haut
#2
Posté 23 septembre 2013 - 10:43
Darin
-
- Members
- 282 messages
Not sure about the area design issue, but the creature design is normal...it loads the appearance when you click on the preview tab, I think, and hence will not update live...there is the appearance editor, but I've found that only works if you run it right after opening the toolset; if the toolset had other things up, the appearance editor will hang up on you. The armor screen should work normal.
#3
Posté 23 septembre 2013 - 03:37
Tchos
-
- Members
- 5 079 messages
Because of the tinting with blueprints, I tend to design the looks of the characters on placed instances, and convert them to blueprints after I'm done, or at least copy and paste their tint colours from the placed instance to the blueprint. You should be able to just click the same blueprint you're working on to load the changes, though. You shouldn't have to select a different one first.
#4
Guest_Iveforgotmypassword_*
Posté 23 septembre 2013 - 03:54
Guest_Iveforgotmypassword_*
Guest_Iveforgotmypassword_*
-
- Guests
I have this problem with making npc's appearances but I've just ignored it and have also found if you click something else then back to the npc it adjusts itself anyway. I could only ever use the appearance editor on my old laptop and since then with bigger and more powerful computers have found it just crashes so I never bother with it.
With the areas sometimes I can't see any lighting adjustments with the environment settings and have to open and close the area but the most annoying one with that is when all my times of day become sunrise and that means opening and closing the toolset.
Then you have the properties window suddenly becoming a big red x with some out of memory nonsense warning in the middle of my screen.. That means a toolset restart too.
My old laptop had 1gb of ram, 125mb of graphics and a 1.6ghz chip so wasn't even supposed to be able to play nwn2 because of its specs but it did and never had any of these issues (King of Shadows fight was a bit jerky though ). So I really don't think it's a case of more ram faster processors or anything like that it's just whether or not your computer likes the way the toolset was made.
Either way we're probably lucky that it still runs on new operating systems.
With the areas sometimes I can't see any lighting adjustments with the environment settings and have to open and close the area but the most annoying one with that is when all my times of day become sunrise and that means opening and closing the toolset.
Then you have the properties window suddenly becoming a big red x with some out of memory nonsense warning in the middle of my screen.. That means a toolset restart too.
My old laptop had 1gb of ram, 125mb of graphics and a 1.6ghz chip so wasn't even supposed to be able to play nwn2 because of its specs but it did and never had any of these issues (King of Shadows fight was a bit jerky though ). So I really don't think it's a case of more ram faster processors or anything like that it's just whether or not your computer likes the way the toolset was made.
Either way we're probably lucky that it still runs on new operating systems.
#5
Posté 23 septembre 2013 - 04:26
Tchos
-
- Members
- 5 079 messages
Glad to know I'm not the only one that gets a big red X in the palettes sometimes.
#6
Guest_Iveforgotmypassword_*
Posté 23 septembre 2013 - 05:14
Guest_Iveforgotmypassword_*
Guest_Iveforgotmypassword_*
-
- Guests
Properties is a bad one because needs a restart the conversation bits aren't so bad as you can use the other ones and a bit of guesswork. I've had all my conversation names disappear from the tab a few times too but with this they're still there and you just have to click them all one by one to make them reappear.
Then again if all this stuff happens with more powerful computers the time you spend restarting the toolset is so tiny with a bigger machine it doesn't make much difference as my old "uncrashable" laptop used to take ages to load everything !
Then again if all this stuff happens with more powerful computers the time you spend restarting the toolset is so tiny with a bigger machine it doesn't make much difference as my old "uncrashable" laptop used to take ages to load everything !
#7
Posté 23 septembre 2013 - 06:32
Lugaid of the Red Stripes
-
- Members
- 955 messages
I'd like to hear an expert chime in on the various ticks and iterations of the .NET framework used by the toolset. Just glancing through the Wikipedia page, I see that the framework has an odd method of garbage collection, pausing the program whenever memory usage reaches a certain threshold to cycle through the data and trash anything that's not being used. I bet some of our crashes happen during those GC cycles.
There also seems to be several security updates, some of which I remember messed up my configuration settings.
We probably need an expert opinion on compatibility, as well. If the .NET has been routinely updated, then 64-bit users probably shouldn't have to run it in compatibility mode, even if they do have to run NWN2 in some sort of compatibility mode, but then again I really have no idea what I'm taking about.
There also seems to be several security updates, some of which I remember messed up my configuration settings.
We probably need an expert opinion on compatibility, as well. If the .NET has been routinely updated, then 64-bit users probably shouldn't have to run it in compatibility mode, even if they do have to run NWN2 in some sort of compatibility mode, but then again I really have no idea what I'm taking about.
#8
Guest_Iveforgotmypassword_*
Posté 23 septembre 2013 - 06:54
Guest_Iveforgotmypassword_*
Guest_Iveforgotmypassword_*
-
- Guests
I don't run it in compatibility mode and I'm on windows 7 64bit. As for routinely updating .NET I don't know if it's happened in the past but I turned off all my updates for everything because they made my printer go fussy and decide to only use genuine cartridges. I refused because I decided it was nothing but a money making racket trying to force me to spend money on more expensive exactly the same ink and I haven't got a printer now.
However that's a good thing because people have to print and send things like forms and official stuff to me now whilst I just wait for the letters and there's more space on my table for my chewed pens and toolset notepads filled with gibberish written in illegible writing.
Not doing anything regarding updates or using compatibility mode could all come about from me installing ( dragging and dropping ) NWN2 on my new PC from an external hard drive where I had all the program files etc. and not the disk.
ps. I don't know what I'm talking about either.
However that's a good thing because people have to print and send things like forms and official stuff to me now whilst I just wait for the letters and there's more space on my table for my chewed pens and toolset notepads filled with gibberish written in illegible writing.
Not doing anything regarding updates or using compatibility mode could all come about from me installing ( dragging and dropping ) NWN2 on my new PC from an external hard drive where I had all the program files etc. and not the disk.
ps. I don't know what I'm talking about either.
Modifié par Iveforgotmypassword, 23 septembre 2013 - 06:58 .
#9
Posté 23 septembre 2013 - 10:39
Dann-J
-
- Members
- 3 161 messages
Tchos wrote...
Glad to know I'm not the only one that gets a big red X in the palettes sometimes.
You can still right-click on things and choose to open the Properties tab as a separate window. At least until you get sick of doing that for every object, creature and blueprint, and finally resort to re-starting the toolset. Or until you click somewhere in the separate window without holding your tongue in the correct way, and it crashes the entire toolset.
#10
Posté 23 septembre 2013 - 10:42
kamal_
-
- Members
- 5 259 messages
Win 8? No ideas, I've never used it.
#11
Posté 24 septembre 2013 - 12:49
Shaughn78
-
- Members
- 637 messages
Okay, so this doesn't look too promising.
Designing stuff was so much easier on the old crappy machine. Armor parts changed and tinting happened as I selected the color. Granted the new computer loads it wicked fast, but my is it a pain to make a few varied NPC to try and kill the PC.
Designing stuff was so much easier on the old crappy machine. Armor parts changed and tinting happened as I selected the color. Granted the new computer loads it wicked fast, but my is it a pain to make a few varied NPC to try and kill the PC.
#12
Guest_Iveforgotmypassword_*
Posté 24 septembre 2013 - 08:04
Guest_Iveforgotmypassword_*
Guest_Iveforgotmypassword_*
-
- Guests
Shaughn78.. I think it's a bit like driving a Ferrari down an old country road, hit a straight part with no bumps and you fly along making up for lost time but when it comes to the bumps something might break and you'll have to go really carefully.
Whereas your old Ford will just take it in it's stride and plod along happily whether there are bumps or not. They both reach the end at the same time it's just that with the Ferrari you are so used to going fast that anything else seems frustrating.
DannJ.. Nice tip I'll remember that if I need to finish off a couple of properties and can't be bothered to do a restart ( that's the tongue in the correct way part of course ).
Whereas your old Ford will just take it in it's stride and plod along happily whether there are bumps or not. They both reach the end at the same time it's just that with the Ferrari you are so used to going fast that anything else seems frustrating.
DannJ.. Nice tip I'll remember that if I need to finish off a couple of properties and can't be bothered to do a restart ( that's the tongue in the correct way part of course ).
#13
Posté 10 octobre 2013 - 09:34
PGB01
-
- Members
- 34 messages
I have the same problem with my new PC, though my laptop which also runs Win8 64bit scales and tints without a hitch. Thus, I am coming to the conclusion that it is the graphics card, or the drivers thereof. I have a GeForce GTX770
in the PC and a mere GT635 in the laptop.
I also have noticed that on opening the toolset my module directory is being formed in the Atari folder rather than in mydocs and I have to save it to mydocs to make it stick there.
Running NWN2 in compatibility mode doesn't seem to have any effect one way or the other.
Still, I am happy that the seven year old coal-fired steam engine runs at all.
in the PC and a mere GT635 in the laptop.
I also have noticed that on opening the toolset my module directory is being formed in the Atari folder rather than in mydocs and I have to save it to mydocs to make it stick there.
Running NWN2 in compatibility mode doesn't seem to have any effect one way or the other.
Still, I am happy that the seven year old coal-fired steam engine runs at all.
