The Witcher 3: Wild Hunt

[Fingolfin269]

I've had times where he doesn't draw a sword and I end up going in with fists until I can roll out of danger and pull the sword manually.

That's the easy mode way. If the game says you only need your firsts then the hard core just use fists!

 

[RaistlinZ]

Also, is there an easy way to disengage from combat and run away?

Sometimes I'm just strolling through the the countryside and get aggro by grey enemies. Geralt puts his fists up to start fighting, and no matter what I try I can't move away or drop out of combat. I try to turn and run, but he just backpedals still facing the enemy with his fists up. Shouldn't I be able to disengage from a fight I don't want to enter?

 

[artemicion]

Also, is there an easy way to disengage from combat and run away?

Sometimes I'm just strolling through the the countryside and get aggro by grey enemies. Geralt puts his fists up to start fighting, and no matter what I try I can't move away or drop out of combat. I try to turn and run, but he just backpedals still facing the enemy with his fists up. Shouldn't I be able to disengage from a fight I don't want to enter?

If you hold down the run/roll button while heading in the opposite direction, he should run away, no?

 

[ImpulsE69]

Man does anyone else have crash to desktop issues with 1.07? I can't seem to play it for more than 10 minutes before it just closes. :/

 

[XiandreX]

Man does anyone else have crash to desktop issues with 1.07? I can't seem to play it for more than 10 minutes before it just closes. :/

Seems fine to me, you overclock?
Maybe its more picky about overclocks... :hmm:

 

[ImpulsE69]

Seems fine to me, you overclock?
Maybe its more picky about overclocks... :hmm:

Yea I read that it was, my card is OC'd by default, I underclocked to reference speeds and it hasn't crashed at all after a couple hours of play.

 

[ImpulsE69]

FFS I hate overlapping issues. I finally get all my W3 issues resolved and they update to 1.08 and now it is broken badly. Crashes as soon as you load the saved game.

EDIT: I found that if I changed all settings to low it would load. If I set it to high/ultra game crashed. I moved to inside a house and saved and restarted the game in low. Then I moved each setting to ultra one by one to see if it would crash. It never did. Once I had everything back on ultra (or set the way it was set before). I went back outside and saved again.

Seems to be working now....wierd.

 

[futurefields]

Seems fine to me, you overclock?
Maybe its more picky about overclocks... :hmm:

Why would a game care if a card is overclocked?

I mean how would it even know?

 

[escrow4]

Why would a game care if a card is overclocked?

I mean how would it even know?

Its not the game the overclock isn't stable. No overclock is ever stable. Ever. Something somewhere will cause it to fart and collapse. Run out of spec and strange stuff happens.

 

[alcoholbob]

Haven't seen any improvements in performance in 1.0.8.

1.0.6 is still my favorite patch, was getting 50% higher fps with Water on High or Ultra since Fullscreen mode was still allowing you to run Nvidia's control panel vsync instead of forcing the choppy in-game vsync on you limiting you to 40fps locked with water tessellation turned up. All 1.0.7/1.08 did was improve Hairworks for me but I don't really care too much about that.

Really wish there was a way to roll back to 1.0.6. Seeing 50% GPU utilization and 15% CPU utilization at 40fps is just painful.

 

[ImpulsE69]

I simply cannot get this game to be stable any longer. I played for hours on end up to 1.06, as of 1.07 it just randomly crashes. In 1.08 now I'm getting random drop offs the map (under it) and still crashes.

 

[futurefields]

Its not the game the overclock isn't stable. No overclock is ever stable. Ever. Something somewhere will cause it to fart and collapse. Run out of spec and strange stuff happens.

You being serious?

 

[ImpulsE69]

You being serious?

Yes, he is. Overclocking for the most part is stable in that it 'should' work flawlessly as long as you aren't stressing the system. However, there is never a guarantee because you are running it out of spec. Witcher 3 is wellknown (apparently) to not play nice with overclocks, even OC'd from the factory cards. There are lots of variables that can play into this. On my old graphics card I OC'd the heck out of it and Witcher 3 ran pretty much flawlessly, so one never knows for sure.

In many cases when something isn't working as expected, one of the first things you will be told to do (from a hardware manufacturers point of view) is to stop overclocking. When in doubt, kill the OC as a test.

 

[Anteaus]

My factory OC 570 GTX was finicky like that. For certain games like Just Cause 2 I had to throttle it down to reference else the game would crash. It was very predictable and the GPU OC was very stable. Some games just don't like overclocking. I can't give you a technical reason....it is what I observed.

Before I upgraded to my 770 GTX, I had a list of games that required me to throttle down else problems cropped up. I suggest you manually throttle factory OC boards down to reference and see if it helps.

 

[futurefields]

Yes, he is. Overclocking for the most part is stable in that it 'should' work flawlessly as long as you aren't stressing the system. However, there is never a guarantee because you are running it out of spec. Witcher 3 is wellknown (apparently) to not play nice with overclocks, even OC'd from the factory cards. There are lots of variables that can play into this. On my old graphics card I OC'd the heck out of it and Witcher 3 ran pretty much flawlessly, so one never knows for sure.

In many cases when something isn't working as expected, one of the first things you will be told to do (from a hardware manufacturers point of view) is to stop overclocking. When in doubt, kill the OC as a test.

Name some?

 

[futurefields]

My factory OC 570 GTX was finicky like that. For certain games like Just Cause 2 I had to throttle it down to reference else the game would crash. It was very predictable and the GPU OC was very stable. Some games just don't like overclocking. I can't give you a technical reason....it is what I observed.

Before I upgraded to my 770 GTX, I had a list of games that required me to throttle down else problems cropped up. I suggest you manually throttle factory OC boards down to reference and see if it helps.

Naturally.

 

[cmdrdredd]

Lol really? So 24 hours stressing my system beyond what any game or program would ever do (IBT, Prime95, memtest) and running 3D mark extreme and loops of Heaven benchmark with no crashes, no errors, and no artifacting it's not stable?? Hardly...not every overclock is stable but it is possible to get a stable overclock if you take the time to find the right clock frequencies for your specific hardware.

 

[ImpulsE69]

Name some?

I probably would have indulged you, but your response to the other post says you are just being obtusely difficult, so if you genuinely care, there's a thing called Google that will tell you all about this subject.

Also, cmdr, should probably do the same thing. :hmm: I do agree, in 99.9% of cases there probably are no anomalous effects, but running out of spec is running out of spec, no matter what your tests tell you. Granted I'm not going to bother going into all the details of this subject, because it involves so much more than just the actual overclock itself and will vary greatly from setup to setup.

I liken it to the "I don't have an issue, so you shouldn't either" statements that seem to run around this forum so much.

What I do know though, is ARRGH this damn game is so unstable for me right now, and I can't tell for certain if it's the game, my card, or it's drivers. Going to RMA the card - just because. It IS the only game giving me problems though and I certainly didn't have these issues prior to changing cards, however, I also did not play 1.07/1.08 on the old card. Might swap them this weekend and see what happens.

 

[cmdrdredd]

I probably would have indulged you, but your response to the other post says you are just being obtusely difficult, so if you genuinely care, there's a thing called Google that will tell you all about this subject.

Also, cmdr, should probably do the same thing. :hmm: I do agree, in 99.9% of cases there probably are no anomalous effects, but running out of spec is running out of spec, no matter what your tests tell you. Granted I'm not going to bother going into all the details of this subject, because it involves so much more than just the actual overclock itself and will vary greatly from setup to setup.

I liken it to the "I don't have an issue, so you shouldn't either" statements that seem to run around this forum so much.

What I do know though, is ARRGH this damn game is so unstable for me right now, and I can't tell for certain if it's the game, my card, or it's drivers. Going to RMA the card - just because. It IS the only game giving me problems though and I certainly didn't have these issues prior to changing cards, however, I also did not play 1.07/1.08 on the old card. Might swap them this weekend and see what happens.

You can have a 100% perfectly stable overclock. It doesn't matter what you say, stable is stable. Ask Intel about it with their K parts and turbo frequencies. Every piece of hardware can have problems even when running at factory settings. Why do you think binning is a thing and companies sell parts with a factory overclock?

 

[futurefields]

I probably would have indulged you, but your response to the other post says you are just being obtusely difficult<snip>

That's incorrect.

I replied to the other guy "naturally" because neither of you gave a real reason why a game would "disagree" with an overclock.

As if a game has a list of all video cards, what their reference clocks should be, and will shut down if it deviates from that at all.

Or something along those lines.

It's ridiculous when you have things like factory OC cards. I didn't even touch the clocks on my 970 and it runs from the factory at 1.4 ghz.

Anyways, you can either substantiate your claim with evidence or accept that it is a bs theory.

 

[ImpulsE69]

You can have a 100% perfectly stable overclock. It doesn't matter what you say, stable is stable. Ask Intel about it with their K parts and turbo frequencies. Every piece of hardware can have problems even when running at factory settings. Why do you think binning is a thing and companies sell parts with a factory overclock?

I think what you are referring to is not entirely the same thing I am referring to. The OC is only one part of the equation. You are saying "because this scenario works" then every scenario will. That simply isn't the case. It doesn't matter if the OC is stable in 99.99% of cases (or 100% for yourself), if one thing does not work with the OC, then that is not 100%. If downclocking resolves that issue, then the OC is not 100% stable, even if the code of the application (or something else short of some other part failure) may be at fault. I think you are trying too hard to disagree with a statement that was originally a blanket statement saying 'something can always go wrong with an OC'. It doesn't mean OC's don't work. I've never had issues with overclocking anything personally.

There are many cases on the web that point to Witcher 3 (and other things in the past - including CPU's) having issues with overclocks. Many of those can probably be tossed aside as some other outlying issue, but workarounds are to stop overclocking.

Or saying it this way: For example (only as example since this thread is about W3) Witcher 3 crashes, the only thing that seems to fix it is to lower clocks (in this case we'll say gpu). That could mean a bad GPU, it could mean a number of things. Then you say, I have another 100 games that run/work perfectly with no issue (at this clock) or even no other program has ever given me problems. That points to W3 being the culprit, however, downclocking the GPU seems to resolve the issue (no other changes). That still doesn't rule out the GPU as being bad, however clearly only W3 has an issue with the OC. That is an unstable OC. It probably points to Witcher 3 exclusively having coding (timing) issues, and that is what is being stated. At least that is my perspective, I can't speak for what escrow said.

I completely agree that it shouldn't be the case, one thing or another needs fixed. either the OC isn't as stable as thought (regardless of test), or the hardware is going bad (which seems unlikely given everything else works), or the program in question has bad coding/tight timings (I normally would go with this one, while ruling out everything else).

 

[cmdrdredd]

Yes I know that which is why I mentioned previously that someone overclocking needs to find the frequency that works for their hardware. Someone with my same cpu can get 4.7 and my chip won't. The voltage required might be different too.

I am contesting the idea that "no overclock is stable ever". That's false

 

[Merad]

Software does not "have an issue with overclocking." The idea is basically ludicrous. You either have a stable overclock or you don't... maybe you didn't realize your overclock was unstable until you played TW3.

 

[futurefields]

Software does not "have an issue with overclocking." The idea is basically ludicrous. You either have a stable overclock or you don't... maybe you didn't realize your overclock was unstable until you played TW3.

This.

 

[ImpulsE69]

Software does not "have an issue with overclocking." The idea is basically ludicrous. You either have a stable overclock or you don't... maybe you didn't realize your overclock was unstable until you played TW3.

*facepalm*

/thread.