ProjectsWhat's NewDownloadsCommunitySupportCompany
Forum Index » S.T.A.L.K.E.R.: Shadow of Chernobyl Forum » Mod discussion
My Global Illumination tests

« Previous 10 events | 1 2 3 4 5 6 7 8 | Next 10 events »| All Messages
Posted by/on
Question/AnswerMake Newest Up Sort by Descending
  11:17:59  14 February 2012
profilee-mailreply Message URLTo the Top
Meltac
messing with code
(Resident)

 

 
On forum: 01/21/2010
Messages: 1519

---QUOTATION---
I'm well versed with GPUs, CPUs... pretty much any hardware really and a good deal of software. A modern GPU will work on the oldest of games, you just might experience weird bugs in games older than DX9 because drivers are no longer optimised for those games. As for DX, I use redist june 2010 (still the newest) and I don't get a problem in any games or other software.
---END QUOTATION---



If so, do you by chance have any suspicion what the problem might be in Derranged's case? If it's not a syntax error nor a hardware nor driver issue, what else might be causing a new GPU not to work with my shaders?
  11:44:16  14 February 2012
profilee-mailreply Message URLTo the Top
Derranged
Senior Resident
 

 
On forum: 04/12/2010
Messages: 1009
It could possibly be my graphics card it'self, dunno. I just really need to get this to start working.
  12:10:07  14 February 2012
profilee-mailreply Message URLTo the Top
Meltac
messing with code
(Resident)

 

 
On forum: 01/21/2010
Messages: 1519

---QUOTATION---
It could possibly be my graphics card it'self, dunno. I just really need to get this to start working.
---END QUOTATION---



What other shader packs did you test? Only vanilla, or maybe Sky4ce or Kingo's? And which options did you enable to produce that crash?
  14:00:45  14 February 2012
profilee-mailreply Message URLTo the Top
ket
Senior Resident
 

 
On forum: 01/13/2006
Messages: 1432

---QUOTATION---
I'm well versed with GPUs, CPUs... pretty much any hardware really and a good deal of software. A modern GPU will work on the oldest of games, you just might experience weird bugs in games older than DX9 because drivers are no longer optimised for those games. As for DX, I use redist june 2010 (still the newest) and I don't get a problem in any games or other software.

If so, do you by chance have any suspicion what the problem might be in Derranged's case? If it's not a syntax error nor a hardware nor driver issue, what else might be causing a new GPU not to work with my shaders?
---END QUOTATION---



It could be a good old fashioned case of the GPU overheating. New shaders with SoC really work a GPU. Even with my system my GPU heats up to around 76c while playing SoC with the new shaders. If its not that I would look into CPU and RAM stability (Intel Burn Test for CPU, HCI memtest for RAM) as they would be other suspects to look at. Depending how old the system is the mainboard chipset & VRMs (in the latters case, if they are heatsinked) could need a new application of TIM, same applied for the CPU.

If none of that fixes the problem I would start looking at software errors. Best way to fix that is to download and use pcdoc pro and tuneup utilities. Once those applications have done their thing run tuneup utilities registry optimiser so it can have a proper look at the registry and not just a quick look which is all it does if you run 1 click maintinence. Once all that is done, downoad and use diskeeper to defrag the HDD then reinstall DX redist june 2010. Fire up Stalker, and see what happens. I wouldn't rule out a corrupt Stalker install at this point either.
  14:32:09  14 February 2012
profilee-mailreply Message URLTo the Top
Derranged
Senior Resident
 

 
On forum: 04/12/2010
 

Message edited by:
Derranged
02/14/2012 14:37:13
Messages: 1009

---QUOTATION---
It could possibly be my graphics card it'self, dunno. I just really need to get this to start working.

What other shader packs did you test? Only vanilla, or maybe Sky4ce or Kingo's? And which options did you enable to produce that crash?
---END QUOTATION---



I haven't tested any others and all options made it crash. The shaders work though, it's just the options which make it fail.


---QUOTATION---
It could be a good old fashioned case of the GPU overheating. New shaders with SoC really work a GPU. Even with my system my GPU heats up to around 76c while playing SoC with the new shaders. If its not that I would look into CPU and RAM stability (Intel Burn Test for CPU, HCI memtest for RAM) as they would be other suspects to look at. Depending how old the system is the mainboard chipset & VRMs (in the latters case, if they are heatsinked) could need a new application of TIM, same applied for the CPU.

If none of that fixes the problem I would start looking at software errors. Best way to fix that is to download and use pcdoc pro and tuneup utilities. Once those applications have done their thing run tuneup utilities registry optimiser so it can have a proper look at the registry and not just a quick look which is all it does if you run 1 click maintinence. Once all that is done, downoad and use diskeeper to defrag the HDD then reinstall DX redist june 2010. Fire up Stalker, and see what happens. I wouldn't rule out a corrupt Stalker install at this point either.
---END QUOTATION---



Nah, my GPU isn't overheating when it crashes on startup, and when it is not even close to 40 degrees Celsius. It's packed with fans and I have set them to go faster when anything becomes hot.

It won't be the CPU or the Ram.. The ram is brand new and my previous ram did the same thing. I have had this CPU since I had my old 5770 and I used Meltacs shaders before with options turned on.

My PC is brand new so it is not old at all.

It's very weird.

I will have a look into those utilities.
  15:12:21  14 February 2012
profilee-mailreply Message URLTo the Top
Meltac
messing with code
(Resident)

 

 
On forum: 01/21/2010
 

Message edited by:
Meltac
02/14/2012 15:13:54
Messages: 1519

---QUOTATION---
I haven't tested any others and all options made it crash. The shaders work though, it's just the options which make it fail.
---END QUOTATION---



Sorry, I still don't get it.

By "options" I assumed you mean the settings that you can specify in the ShaderSettings.txt file. Then if so, what do you mean by "all options made it crash"? I mean, that whole file consists only of options, and most of them are enabled by default, so did you first disable all of them and the shader worked, and after you re-enabled one of them it crashed? Or what exactly did you do to ensure the shader itself works?

@ket: I understand there might be several hardware/drivers/firmware or whatever reasons to make the game crash with some GPU-intenive shader pack (like mine).

However, what I do not understand: The error message he's getting is thrown while the shaders' source code is compiled upon game startup. So as I said it normally indicated that something in the shader's source code is not valid.

Now at that point there has none of the shaders been actually executed yet, so why should a GPU-/CPU-/RAM-related issue arise in that situation? If it was one, shouldn't the game crash earliest in the main menu, or even more likely, after a savegame has been reloaded, i.e. when the engine actually starts shader processing?
  16:10:37  14 February 2012
profilee-mailreply Message URLTo the Top
Derranged
Senior Resident
 

 
On forum: 04/12/2010
Messages: 1009

---QUOTATION---
I haven't tested any others and all options made it crash. The shaders work though, it's just the options which make it fail.

Sorry, I still don't get it.

By "options" I assumed you mean the settings that you can specify in the ShaderSettings.txt file. Then if so, what do you mean by "all options made it crash"? I mean, that whole file consists only of options, and most of them are enabled by default, so did you first disable all of them and the shader worked, and after you re-enabled one of them it crashed? Or what exactly did you do to ensure the shader itself works?

@ket: I understand there might be several hardware/drivers/firmware or whatever reasons to make the game crash with some GPU-intenive shader pack (like mine).

However, what I do not understand: The error message he's getting is thrown while the shaders' source code is compiled upon game startup. So as I said it normally indicated that something in the shader's source code is not valid.

Now at that point there has none of the shaders been actually executed yet, so why should a GPU-/CPU-/RAM-related issue arise in that situation? If it was one, shouldn't the game crash earliest in the main menu, or even more likely, after a savegame has been reloaded, i.e. when the engine actually starts shader processing?
---END QUOTATION---



Yes, that is what I mean. Yes, you have some of them on but when I go to turn on more it just fails....
  16:19:50  14 February 2012
profilee-mailreply Message URLTo the Top
ket
Senior Resident
 

 
On forum: 01/13/2006
 

Message edited by:
ket
02/14/2012 16:24:21
Messages: 1432

---QUOTATION---
It could possibly be my graphics card it'self, dunno. I just really need to get this to start working.

What other shader packs did you test? Only vanilla, or maybe Sky4ce or Kingo's? And which options did you enable to produce that crash?

I haven't tested any others and all options made it crash. The shaders work though, it's just the options which make it fail.

It could be a good old fashioned case of the GPU overheating. New shaders with SoC really work a GPU. Even with my system my GPU heats up to around 76c while playing SoC with the new shaders. If its not that I would look into CPU and RAM stability (Intel Burn Test for CPU, HCI memtest for RAM) as they would be other suspects to look at. Depending how old the system is the mainboard chipset & VRMs (in the latters case, if they are heatsinked) could need a new application of TIM, same applied for the CPU.

If none of that fixes the problem I would start looking at software errors. Best way to fix that is to download and use pcdoc pro and tuneup utilities. Once those applications have done their thing run tuneup utilities registry optimiser so it can have a proper look at the registry and not just a quick look which is all it does if you run 1 click maintinence. Once all that is done, downoad and use diskeeper to defrag the HDD then reinstall DX redist june 2010. Fire up Stalker, and see what happens. I wouldn't rule out a corrupt Stalker install at this point either.

Nah, my GPU isn't overheating when it crashes on startup, and when it is not even close to 40 degrees Celsius. It's packed with fans and I have set them to go faster when anything becomes hot.

It won't be the CPU or the Ram.. The ram is brand new and my previous ram did the same thing. I have had this CPU since I had my old 5770 and I used Meltacs shaders before with options turned on.

My PC is brand new so it is not old at all.

It's very weird.

I will have a look into those utilities.
---END QUOTATION---



Look at your PSU and let me know how many amps (A) the 12v rail has. If your 12v rail is weak that will be the source of your instabilities.
  16:56:31  14 February 2012
profilee-mailreply Message URLTo the Top
Derranged
Senior Resident
 

 
On forum: 04/12/2010
 

Message edited by:
Derranged
02/14/2012 16:57:39
Messages: 1009
I am using a Top Brand PSU (Corsair HX520W Modular PSU) and I know it isn't the problem.

http://forums.overclockers.com.au/showthread.php?t=625374

On their it says it gets 18A on the 12V1, 12V2, 12V3...

EDIT: But, I am running on 2 PSU's...

My main Corsair and my Graphics card one...

My graphics card PSU is a Thermal Take one and I don't think it would be the problem.
  17:10:36  14 February 2012
profilee-mailreply Message URLTo the Top
ket
Senior Resident
 

 
On forum: 01/13/2006
Messages: 1432
Running on 2 PSUs generally isn't the brightest of ideas. 18A on each rail isn't overly high either. Even mid-range graphics cards tend to require a rail with a good 24A or more. I'm certain your issue is system specific and not anything to do with the game or shaders. Knowing every detail about your system would be useful.
 
Each word should be at least 3 characters long.
Search:    
Search conditions:    - spaces as AND    - spaces as OR   
 
Forum Index » S.T.A.L.K.E.R.: Shadow of Chernobyl Forum » Mod discussion
 

All short dates are in Month-Day-Year format.


 

Copyright © 1995-2021 GSC Game World. All rights reserved.
This site is best viewed in Internet Explorer 4.xx and up and Javascript enabled. Webmaster.
Opera Software products are not supported.
If any problem concerning the site functioning under Opera Software appears apply
to Opera Software technical support service.