Is there any particular reason for the -10.0 minimum for both Z position and Z translation in the "adjust location" window? I've tried using a memory editor to set it to lower and I haven't run into any problems yet.
Was wondering if that limit could be removed so I don't have to use a memory editor to properly place tall, scaled objects.
Was going to leave this at support.beamdog.com but I got a big security risk window pop up on firefox when I clicked your link in first post.
Anyhow it seems a bug that was fixed is back? I deleted an area that had the start location. Went to save the module. It gave the warning that the module needs a valid start location. Tried to place a new one in a valid area. Got access violation error. Kept trying and eventually the toolset crashed.
Another smaller thing. If you have a placeable properties open and hover over each of the tabs(basic, lock, trap, etc), it displays the message at the bottom left corner "press this button to save all changes" same as the "OK" button. I checked to make sure It does not do it for creatures or items. It doesn't.
Is any one else getting an error every time you load the toolset, I have tried on multiple laptops. some using a nevidia card others using the integrated graphics. I recently reinstalled the game through gog and got the update but now toolset is broken, I have 4 different gog accounts for my kids and my self toolset will not work on any of the computers. normal game works fine
Quick question. Is there a reason in task manager it says the toolset is 32-bit? I thought with the patches everything automatically updates. I thought 8193 would be 64.
Currently running on Acer Nitro AN515-54, Windows 10 Home, Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz, 4 Cores, 8GB DDR4 Memory, NVIDIA GeForce GTX 1650.
I just wanted to report that in the model preview window, armor and clothing seems to be rendered using the Compatibility Mode (16 meg) texture quality. Although, it is rendered in the game according to what texture quality is enabled. I remember experiencing this same issue after a fresh install of NWN Classic back in the day. Running the game's system detection utility usually fixed it. Unfortunately, NWN:EE doesn't seem to have a program resembling that utility anywhere in the game's location. Has anyone else experienced this issue, and is there a way to correct it? Thank you for reading, and happy (healthy) gaming to all.
@Prince_Raymond The toolset has a texture quality level just like the game does, in its options panels. However, since they aren't on the front page of the the often used video options in the game client, and most people do not spend a lot of time in the toolset options menu, not all players know about the setting.
Meanwhile, the default setting for toolset texture quality isn't "Compatibility Mode (16 meg)" nor "64 meg or higher", it is a 5th option the game doesn't have, "Use the same setting as the game".
This checks the nwn.ini to see which texture quality nwmain.exe is currently using, however, texture quality stopped being stored in nwn.ini in a recent 8193 patch, and is now stored in settings.tml, and the toolset will need to be updated to check there instead.
Without the parameter in nwn.ini, the setting matching fails, and it probably falls back to the first option, Compatibility Mode (16 meg).
You can uncheck the feature to match the nwn.ini setting, and manually choose 64 meg, and the game's textures (not just in the preview area, everywhere) will now use the highest available textures that are additionally supplied as overrides from the game's texture packs.
It's worth noting that a lot of game assets don't come with multiple texture versions, especially the material added in 1.69. In such cases the only texture available is as "high quality" as the 64 meg enabled textures, and is still used in Compatibility mode (No texture packs loaded).
@Symphony It worked! Thank you very much, kind sir. While we're on the subject of issues, I just noticed something odd happening every time I type "www.beamdog.com" (without quotation marks) in the address bar of my browser. Instead of loading the home page, it downloads a 57-byte size file to my computer. I have had Norton scan this file, and no threats were detected. Has anyone else experienced this?
@JuliusBorisov Thank you, sir. After doing some testing, I have found that the home page will load normally if I type what I mentioned above after previously visiting the home page without closing my browser. I currently have it set to clear all my browsing data every time I close my browser. This issue has reproduced on both the latest versions of Microsoft Edge and Google Chrome after all browsing data has been cleared. I hope this information helps. Please feel free to move this to the appropriate thread since this doesn't have any correlation with the toolset. Thank you for reading, and happy (healthy) gaming to all.
@JuliusBorisov Thank you, sir. After doing some testing, I have found that the home page will load normally if I type what I mentioned above after previously visiting the home page without closing my browser. I currently have it set to clear all my browsing data every time I close my browser. This issue has reproduced on both the latest versions of Microsoft Edge and Google Chrome after all browsing data has been cleared. I hope this information helps. Please feel free to move this to the appropriate thread since this doesn't have any correlation with the toolset. Thank you for reading, and happy (healthy) gaming to all.
While not strictly toolset, could I make a couple of suggestions that would be (well I think they would be) very useful changes to NwHak please. As far as I can tell both changes should be rather simple to implement too. Firstly could you make windows associate hak files with NwHak. I've tried to do it myself to no avail and it appears, if possible, it has to be done on installation of NwHak. The second suggestion is to slightly change the behaviour of NwHak so that instead of truncating overlong filenames when they are added but instead just issue a warning message. Currently it is too easy, when adding shader maps, to end up with multiple image files with exactly the same name.
I would like to make a suggestion, can we replace the conversation editor with flamewinds v2.0 version. So much better and shouldn't be too hard to do. Flamewind is open source now.
I would like to make a suggestion, can we replace the conversation editor with flamewinds v2.0 version. So much better and shouldn't be too hard to do. Flamewind is open source now.
Comments
Was wondering if that limit could be removed so I don't have to use a memory editor to properly place tall, scaled objects.
Anyhow it seems a bug that was fixed is back? I deleted an area that had the start location. Went to save the module. It gave the warning that the module needs a valid start location. Tried to place a new one in a valid area. Got access violation error. Kept trying and eventually the toolset crashed.
Another smaller thing. If you have a placeable properties open and hover over each of the tabs(basic, lock, trap, etc), it displays the message at the bottom left corner "press this button to save all changes" same as the "OK" button. I checked to make sure It does not do it for creatures or items. It doesn't.
I just wanted to report that in the model preview window, armor and clothing seems to be rendered using the Compatibility Mode (16 meg) texture quality. Although, it is rendered in the game according to what texture quality is enabled. I remember experiencing this same issue after a fresh install of NWN Classic back in the day. Running the game's system detection utility usually fixed it. Unfortunately, NWN:EE doesn't seem to have a program resembling that utility anywhere in the game's location. Has anyone else experienced this issue, and is there a way to correct it? Thank you for reading, and happy (healthy) gaming to all.
Meanwhile, the default setting for toolset texture quality isn't "Compatibility Mode (16 meg)" nor "64 meg or higher", it is a 5th option the game doesn't have, "Use the same setting as the game".
This checks the nwn.ini to see which texture quality nwmain.exe is currently using, however, texture quality stopped being stored in nwn.ini in a recent 8193 patch, and is now stored in settings.tml, and the toolset will need to be updated to check there instead.
Without the parameter in nwn.ini, the setting matching fails, and it probably falls back to the first option, Compatibility Mode (16 meg).
You can uncheck the feature to match the nwn.ini setting, and manually choose 64 meg, and the game's textures (not just in the preview area, everywhere) will now use the highest available textures that are additionally supplied as overrides from the game's texture packs.
It's worth noting that a lot of game assets don't come with multiple texture versions, especially the material added in 1.69. In such cases the only texture available is as "high quality" as the 64 meg enabled textures, and is still used in Compatibility mode (No texture packs loaded).
We have fixed the site issue.
Make sure to uncheck the static checkbox in the placeable's properties
Thanks for reading.
TR
https://neverwintervault.org/project/nwnee/other/tool/flamewind-conversation-editor-20
Could use this perhaps?
Note, these two may become obsolete should BD update the graphics update.
TR