
Mashiki
Members-
Posts
107 -
Joined
-
Last visited
Everything posted by Mashiki
-
Post your swinfo.txt file and we'll take a look from that point on. You can clip off the keymapping part tho.
-
[SOLVED] Black screen after movies
Mashiki replied to Johno's topic in Star Wars: General Discussion
4.10's are unstable on Kotor2, and will cause crashing even on stable setups. -
This is why people buy Xbox
Mashiki replied to sanitystream's topic in Star Wars: General Discussion
Nah. I've seen shoddy releases...it was called the Ruins of Myth Drannor. What happens here is you get a good dev. team backed into a corner by a publisher who says "NOW" and that's it. No up, no down, no way around it. When I worked in heavy manfg. it was similar when we rolled out new products. Even if the stuff wasn't ready(bug in PLC programing or controller failures, etc), it would be shipped and fixed later. That should tell you the state of the world. Ofcourse when KoTOR was released the forums were filled with posts just like this as well. It dies in time... -
Crystal disappeared from lightsaber
Mashiki replied to Sorwen's topic in Star Wars: General Discussion
Yup. I sent in a email to LA on this one...rubart or something. +1 atk +1dmg? I can't remember the name of the crystal but the bonus was still there. -
Radeon owners: Post driver success here!
Mashiki replied to jasontiller's topic in Star Wars: General Discussion
To make it simple, the way driver calls are made into the programing interface are different. The best solution is to uninstall your current CAT set, use the CAT cleaner, then install the 4.11 CAT's. Some people have had limited sucess in getting the above method to work, other times it doesn't work at all and it simply locks the game hard. You can *try* it out if you want, but if it doesn't work just delete the DLL file from your KOTOR2 directory. -
help:3Dlabs Oxygen VX1 (AGP)64mb user+OpenGl1.4.0
Mashiki replied to John Goa's topic in Star Wars: General Discussion
In the end with the Oxygen cards you are left with no luck. They are not upto snuff to play anything new. That's the hard reality of this problem. I doubt that they've made drivers, you could check the OGL consortium website http://www.opengl.org/ , but don't hold your breath. The next option is to buy another video card. Up here in Canada you can get away with a regular ATI 9600 for around $120, which will last you atleast a little while anyway. -
You are getting help. Don't play on a notebook is good advice. Second thing is try running memtest86+ and then running PRIME95 for 48hrs or so to see if you have hardware failure. 'Leaving' a notebook running and using it for say browsing and word processing is diffrent in memory utilization and writes compared to the way a game utilizes memory and writes it. Remember Doom3 and the problems people had with OC'd cards? Perhaps not...problems was...chips were operating out of spec on the video card, that caused errors and the game would crash, lock up or do other 'weird' things.
-
Radeon owners: Post driver success here!
Mashiki replied to jasontiller's topic in Star Wars: General Discussion
-
Radeon owners: Post driver success here!
Mashiki replied to jasontiller's topic in Star Wars: General Discussion
I have to agree, the 4.11 cat's are the best. I went to dantoonie and experienced 'teleporting' similar to the original KoTOR release. I dropped the 4.11 OGL core into the KoTOR2 directory and it worked just fine, actually it worked better then fine. Not only is it smoother but it's twice as fast. For those that want to try it on a NON X800 series card...I'll give you instructions. This only works if you have a higher driver set. 1) Download the Catalyst 4.11 2) Open using Winzip(or winrar) - look for the file called atioglxx.dl_ 3) Extract to your "KOTOR2" Install Directory. (make sure "Use Folder Names" is turned off) 4) Start->Run "cmd" for a standard command prompt. 5) type: expand YOUR KOTOR2 PATH\atioglxx.dl_ atioglxx.dll For those who don't follow the "your KOTOR Path" it should be something like C:\Program Files\LucasArts\SWKotOR2\ This will change the OpenGL handler from the higher 4.12-5.2 that it's currently using to the 4.11 without changing the core drivers of your system. Only applies to this game. Mess something up. Not my problem. Game doesn't work anymore, not my problem either. -
Radeon owners: Post driver success here!
Mashiki replied to jasontiller's topic in Star Wars: General Discussion
Arclam interesting. If your point holds then dropping the atioglxx.dll from the 4.11 in the Kotor2 directory should be a good fix for that. I haven't gotten far enough to test it out, I'll post an update when I get that far. -
reboot the machine, drop to a command prompt from inside windows and delete them by typing in : del filename.ext don't forget to change to the kotor2 directory first. It should be c:\program files\lucasarts\swkotor2\ If the files are locked, you may have HDD errors or disk locking issues that can't be resolved easily. Another possiblity is a process is locking the HDD and preventing the installer from working properly.
-
Select the behavior you want then click on it. That should lock it.
-
Radeon owners: Post driver success here!
Mashiki replied to jasontiller's topic in Star Wars: General Discussion
Graphics: ATI 9600XT 128(Asus) Cats: 5.2 Gameplay since driver upgrade: 5.5hrs - No crashes, I haven't seen any slowdowns either. I haven't had a chance to test expanded or large enviroments tho. -
If you want to attack those people then do so, I did not say anything to you like that. In that light...grow up. Omega's 4.11 cats are a mixture of two different driver sets, I can't remember which two however since I don't keep track anymore. What you have is 'luck' nothing else. What works for you may not work for someone else, that is reality.
-
I've I'ready done driver drops into the KoTOR directory, 4.11's to 5.2's are the only ones which will work in a 'solid' way. Anything lower then that and you'll get a speed increase...but it will introduce massive instability into the system. If you are unfamiliar with what I'm talking about, with OGL games, you can take a copy of the OGL extender from a driver set and place it into it's directory. In most cases it will then be forced to use the first OGL driver it finds. I did I write up on how to do it on the bioware forums a few months agowhen the 4.12 cat's re-introduced the slowdown problem, and the older cat's were the best solution. This doesn't work on x800 series cards unfortunatly...but does work on all the older chipsets. So if you find one driver set which works really nice then you can just use that. I'll be fully installing the 5.2's tonight when I get a few mintues tho.
-
Can't get off the Harbinger!!
Mashiki replied to Zeroshadow's topic in Star Wars: General Discussion
Post a copy of swinfo.txt file here. You can clip off the keymapping bit tho. -
I'll put it simply. Don't use a laptop to play PC games, core componets in mobile chips that are in desktop chipsets are missing to save power. Two points for the disc's, either they are bad or something is wrong with the laptop but if you are 'throwing' it around like that you don't treat your hardware worth anything to begin with so it shouldn't be a surprise.
-
Normal gameplay, I've seen two CTD's in 5-6hrs of gameplay. I usually reboot after each crash.
-
It does sound like a bad disc. Try getting a direct exchange from your retailer, explain to them exactly what the problem is.
-
(PC)Woodstock, Ontario(Can) is where I got my copy. On Feb 8th @ 9pm-ish, very impressed with it so far.
-
I'm gonna try a 4.7 drop in the Kotor2 directory and see how that works, I'll post a reply in a bit. I'm starting to see slowdowns on Peragus. edit: 4.7's are faster but cause massive instability in the engine, same with 4.8-4.10's. 4.11- 4.12's are okay and so are 5.1's. I haven't tried 5.2's yet. This is the 'real' big thing, if the game is crashing for no reason. It's the video drivers. Anything lower then 4.11's seem to cause massive crashes, lockup's and black screens.
-
Faulting application swkotor2.exe, version 2.0.0.0, faulting module swkotor2.exe, version 2.0.0.0, fault address 0x0017503b. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 73 77 6b ure swk 0018: 6f 74 6f 72 32 2e 65 78 otor2.ex 0020: 65 20 32 2e 30 2e 30 2e e 2.0.0. 0028: 30 20 69 6e 20 73 77 6b 0 in swk 0030: 6f 74 6f 72 32 2e 65 78 otor2.ex 0038: 65 20 32 2e 30 2e 30 2e e 2.0.0. 0040: 30 20 61 74 20 6f 66 66 0 at off 0048: 73 65 74 20 30 30 31 37 set 0017 0050: 35 30 33 62 0d 0a 503b.. If you've got a clue on it great, if not then fine. Access the main control panel in Pergaus...caused a CTD. Yes and if you really need PC info then ask. I'll post it later.
-
Using 5.1 Cat's here on a 9600xt(asus), it seem to be very smooth so far. It doesn't have the problems that KoTOR has. I ran into that problem last night on Dantoonie(sp?) I'll update later if I run into any problems.
-
KOTOR 2 has officially shipped (PC)
Mashiki replied to Black Raven's topic in Star Wars: General Discussion
Well it's out for sure. I managed to snag a copy a few minutes ago....too bad I've got work to do before I play it. Woodstock Walmart has 6 copies left. -
has the pc version been released today?
Mashiki replied to NeverwinterKnight's topic in Star Wars: General Discussion
Well I called the EB's in my area(London, Ontario) and none of them have it. They said they'll have theirs in tomorrow(9th) with any luck.