5 réponses à ce sujet

[Rubies]

I'm not really sure if this belongs in the Custom Content forum, it's... sort of custom content, I suppose!

When nwmain is named anything other than "nwmain.exe" and ran, it has issues with the Environment Maps video setting (rendering players as invisible, as well as the compass/etc). Can be recreated by making a copy of NWMain.exe and firing it up with Environment Maps checked. I'm assuming this is some sort of hacky fix specifically for NWN's executable (possibly an ATI specific thing, or am I way off here)?

Is there any way to force this for other executables, or identifying it with another name by editing the executable itself for the purposes of addressing this? It's becoming really irritating to have to switch between two filenames in order to test out executable edits. ._.

Modifié par Rubies, 24 juillet 2012 - 04:14 .

[Lightfoot8]

Hmm,  Having problems from having a differant name is new to me, but I have never tried changing the name of the .exe
Have you tried just keeping your haked .exe in a differant folder keeping the same name and just creating a shortcut to run the .exe in the original folder.  

Perhaps a picture will help me explain my Idea. 



The 'Target' field above would need to point  the haked EXE along with any command line options, Like starting the DM client above.  

The 'Start in' field would need to point to the folder  you want the executable to run in.  

That should allow you to have several haked versions with the same name(differant locations) all running in the same game folder.

You can even place all of the shortcuts in the same folder or on the desktop, since the shortcut does not have to have the same name as the .exe.

Tottaly untested on my part, but it is worth a shot.

Modifié par Lightfoot8, 24 juillet 2012 - 05:00 .

[Rubies]

Um, that only works with shortcuts, doesn't it? I don't think executables even have a Shortcut tab thingymajig. Thanks for the suggestion, though! D:

[Lightfoot8]

Correct the executable does not have the shortcut tab. You create a shortcut for the executable. Editing the 'Start in' field for the short cut should change the 'Working Directory' for the Executable.

Executable Loaded from 'Target Field' but runs as if it was started in the 'Start in' field.
So you will need both the Haked Server and a Shortcut to change the Working Directory.

[Rubies]

Oh I understaaaaand, I think... I'll give it a shot, thanks!

[Rubies]

That works! I'm ecstatic, it's taken me -forever- to try and work around that and the solution is kinda simple. /cringe

Thaaaanks!