
Installation program telling me Widescreen mod not installed
#1
Posted 18 November 2009 - 03:34 PM
Does anyone have any idea what the problem might be? Would be very gratefull for any answears that can solve the problem as im really looking forward to a new runthrough after so many years!
Thank you // Gustav
btw im installing with these instructions:
http://thunderpeel20...lly-modded.html
#2
Posted 18 November 2009 - 11:50 PM
Did you install widescreen in one of the supported resolutions? If you install in other than 1280x1024 or 1280x720 or 1280x800, you'll run into trouble, possibly of this kind.
Also, what operating system are you running?
Edited by Markus Ramikin, 18 November 2009 - 11:53 PM.
#3
Posted 19 November 2009 - 12:16 AM
Until the people in charge respond, the only thing that comes to mind is:
Did you install widescreen in one of the supported resolutions? If you install in other than 1280x1024 or 1280x720 or 1280x800, you'll run into trouble, possibly of this kind.
Also, what operating system are you running?
#4
Posted 19 November 2009 - 08:21 AM
You'll find a file in the installation folder named "SETUP-GHOSTDOG'S-PST-UI.DEBUG". Can you attach it here?
#5
Posted 19 November 2009 - 08:41 AM
Attached Files
#6
Posted 19 November 2009 - 09:34 AM
Here is the debug file
Let me guess, you have Vista? If so, you need to install the game to a non Program Files sub-folder, this is cause the files are protected by Vista and mirrored elsewhere, so none of the files are actually read correctly.WARNING: parsing log [WeiDU.log]: Sys_error("WeiDU.log: No such file or directory")
Or you actually hadn't installed the Widescreen mod yet... or an other WeiDU mods...
And let's remember that the Widescreen mod need to be installed first, before the Ghostdog's PS:T UI mod.
Edited by Jarno Mikkola, 20 November 2009 - 03:01 AM.
Deactivated account. The user today is known as The Imp.
#7
Posted 19 November 2009 - 10:37 AM
#8
Posted 19 November 2009 - 02:43 PM
edit: tested other resulutions, same thing
Well he said he was using windows xp. From the Debug you can see that my mod detects an unsupported resolution. If you have installed the widescreen mod correctly at a 1280x800 resolution, then there must be some other problem, but it's the first time something like that has come up. There could be some offset value mistake from my part, but it's unlikely since it should have been mentioned by others. Do you have the 2cd or the 4cd version of torment? Could you try installing one of the other resolutions and see if it works ?
Edited by Bescheid, 19 November 2009 - 02:48 PM.
#9
Posted 20 November 2009 - 02:57 AM
Well, as Jarno says, this problem might be related with this warning found in the debug file "WARNING: parsing log [WeiDU.log]: Sys_error("WeiDU.log: No such file or directory")" . It shouldn't be there. Have you by any chance installed torment in some protected folder ? I know you're not using vista, but maybe some antivirus/security program is protecting this folder ? It seems that the mod can't find/write on the weidu.log. Have you installed Qwinn's mods (fixpack, UB, tweaks) successfully?
Edited by ghostdog, 20 November 2009 - 02:58 AM.
#10
Posted 20 November 2009 - 07:47 AM
Wery well now i tried starting the game and i get this message: An Assertion failed in F:\Torment\Source\chitin\ChDimm.cpp at the line number 787
and the game wont start, any clue of what might be wrong now?
// Gustav
This is very strange. Are you certain you've followed every step of the installation correctly ? I assume you're using the latest version (v2.2) of the widescreen mod, right ?
Well, as Jarno says, this problem might be related with this warning found in the debug file "WARNING: parsing log [WeiDU.log]: Sys_error("WeiDU.log: No such file or directory")" . It shouldn't be there. Have you by any chance installed torment in some protected folder ? I know you're not using vista, but maybe some antivirus/security program is protecting this folder ? It seems that the mod can't find/write on the weidu.log. Have you installed Qwinn's mods (fixpack, UB, tweaks) successfully?
Edited by Bescheid, 20 November 2009 - 07:48 AM.
#11
Posted 20 November 2009 - 08:01 AM
Open the Torment.ini and make sure the [Alias] headers point to the right folders.Very well now i tried starting the game and i get this message: An Assertion failed in F:\Torment\Source\chitin\ChDimm.cpp at the line number 787
and the game wont start, any clue of what might be wrong now?
Google is your friend. Yes, that's for BG2, so the line numbers is different for PS:T.
Deactivated account. The user today is known as The Imp.
#12
Posted 20 November 2009 - 08:43 AM
Open the Torment.ini and make sure the [Alias] headers point to the right folders.Very well now i tried starting the game and i get this message: An Assertion failed in F:\Torment\Source\chitin\ChDimm.cpp at the line number 787
and the game wont start, any clue of what might be wrong now?
Google is your friend. Yes, that's for BG2, so the line numbers is different for PS:T.
Yeah, this whole thing sounds like you haven't done the full install properly. Look here for instructions on how to do it.
for comparison in my ini it looks like this :
[Alias] HD0:=c:\games\Torment CD1:=F:\cd1 CD2:=C:\Games\Torment\TDATA\cd2 CD3:=C:\Games\Torment\TDATA\cd3 CD4:=C:\Games\Torment\TDATA\cd4 CD5:=F:\CD5
#13
Posted 20 November 2009 - 08:49 AM

but i have done as they say over in the "alpha"-forum and have the video mode costomized to allow the resolution, what else could be wrong here?
Open the Torment.ini and make sure the [Alias] headers point to the right folders.Very well now i tried starting the game and i get this message: An Assertion failed in F:\Torment\Source\chitin\ChDimm.cpp at the line number 787
and the game wont start, any clue of what might be wrong now?
Google is your friend. Yes, that's for BG2, so the line numbers is different for PS:T.
#14
Posted 20 November 2009 - 10:05 AM
#15
Posted 20 November 2009 - 10:10 AM
Edit: Think i solved it! When costomizing the resulution in the Nvida control panel u need to change from 32 bit to 16 bit, then it seems to work! One little thing they seem to have forgotten to mention.
If you're sure that your card's control panel has the resolution you're trying to use as a viable one, then something may have gone wrong during all those installations/uninstallations. The only thing I can propose is to make a new install of everything.
Edited by Bescheid, 20 November 2009 - 10:28 AM.