701 réponses à ce sujet

[Verrenus]

First of all, a very Happy New Year to everyone here! May 2015's games run flawlessly on your rigs and bring you many great gaming moments! 

 

hey there, first of all, happy new year everybody 

I just wanted to share this: By enabling adaptive vsync and setting pre-rendered frames to 4 in Nvidia Control Panel the game started to play much smoother.I haven't experienced any input lag either.

 

Though, my only problem with adaptive vsync is, i get tearing as soon as the FPS hits 59 

 

I've experiencing tearing with Adaptive V-sync forced on myself, but they seem to have lessened since I force Triple Buffering off in the "user.cfg" file. Maybe this is something you would like to try as well, just to see if it helps? 

 

     I tried for about 2 weeks to get this game to work,pre-patch and after. Continious CTD`s and a few BSOD`s and DX errors.I tried all the fixes posted here and elsewhere but had no joy.I did manage a complete play through because sometimes the game would run for a few hours with no glitches.It was an extremely frustrating play through.lol

     I got a nice bonus for Christmas so splashed out on a GTX970 and 850W power supply.The game ran fantastic......for 20 mins:( Started getting various BSOD`s then my DVD player stopped working.I`d had this before on an older system so knew how to remedy this.Didn`t work as my boot partition was trashed.

After a couple of days pulling my remaining hair out i finally managed,after a complete reinstall of my OS, to get my rig working again.

    I played Skyrim with about 20 mods for a few hours with no problems (don`t throw bricks please:)) then tried the game again on low settings,windows full screen and no overlays.The usual CTD`s,DX errors occured and the BSOD`s became rampant.Though i`d already ran all the memory tests and hardrive checks i did them again.All passed after long hours testing.

    At this point i was seriously considering buying a new rig as my current one was very close to flying out the window along with my digitally downloded DA:I.

When you get really frustated because you think you have tried everything you suddenly remember something you read somewhere .....try using other memory chips.I didn`t think it was worth it as i`d checked my memory so many times but i had 4GB memory sitting in my old rig,so even though i doubted the game would run on that paltry amount i swapped it in.Guess what?  The game run fine on low settings for 10 hours.Loading times were slow but the game run without any problems.

Next day i bought 16GB of memory and the game is flying.Ultra settings and about 20 hours play with no crashes.

   My conclusion is before you try anything else get your hands on some different memory chips,steal them from your wives computer or even get your best mate drunk:)

   Happy New Year everyone.

 

Wow, that is a great story indeed, thank you very much for taking the time to share it with us! 

 

The BSOD error codes would have probably led you to pinpointing the problems to your RAM sooner, but I'm really glad to hear that you pulled through these tough times. While most RAM sticks will work well with all compatible motherboards, there are some that might cause problems, such as you've been experiencing, without being detected as faulty by MEMTEST+. This is why all motherboard manufacturers provide a qualified vendor list detailing the RAM compatibility that they themselves tested with that particular motherboard model. It's not normally necessary to consult it, but when you're facing issues such as yours, it's definitely worth checking if your RAM has been validated by your motherboard manufacturer, just to safe! 

 

I had one or two BSOD a year ago. All of the sudden. I searched for a while till I found something. Windows told me in the systems panel that I had 12 GB memory installed but could only use 8 GB of them. So I started to test my RAM. I have three memory sticks and I tested them one after another. I installed just one of them, started Windows, all was fine. Installed one of the other sticks, test again, all fine and so on. All three sticks were working fine. Then I put them all three back into my rig and no more BSOD. Some kind of connection problem, dust or whatever. This problem may come back any time. But in the next two months I want to get me a new rig. 

 

It's indeed possible that the memory modules were incorrectly seated in the first place, or that there was dust present in the socket, which invariably leads to a BSOD sooner or later. It's great to hear that you managed to get around it and had no other major problems with your rig since! If you're planning on building a new rig yourself soon, then I can help you with some component picking, or at least give you some helpful websites for you to browse and decide for yourself!

[Influ]

hey there, first of all, happy new year everybody 

I just wanted to share this: By enabling adaptive vsync and setting pre-rendered frames to 4 in Nvidia Control Panel the game started to play much smoother.I haven't experienced any input lag either.

 

Though, my only problem with adaptive vsync is, i get tearing as soon as the FPS hits 59 

The way adaptive vsync works is by toggling it on and off based on your framerate. At the monitor's refresh rate and above vsync is on, but if you drop below it, vsync is toggled off. That's why you'll encounter tearing at lower framerates.

[Nauticle]

So Ive installed Windows 10 but unfortunately Im running into an issue with my phone preventing me from logging into Origin. Im hoping to get a code received soon but it may take until tomorrow before I finally get to test DAI on here. I had no problems installed Nvidia drivers or Origin though so that's a good sign.

[ARGranati]

Any way to make the world less "shinny" like disabling bloom or making metal armor/tacks/glass/hair/mustaches/belts/barrels/everything not shine so damn much???

[Verrenus]

The way adaptive vsync works is by toggling it on and off based on your framerate. At the monitor's refresh rate and above vsync is on, but if you drop below it, vsync is toggled off. That's why you'll encounter tearing at lower framerates.

 

I've finally tracked down the excessive tearing I was getting before even when panning the camera around during conversations to the GameTime.MaxVariableFps command. Apparently, even setting it to the recommended value of 0.01 frames below your actual refresh rate causes incredible amounts of tearing and that is with Adaptive V-sync enabled!

 

I've since removed the command from my "Game Properties" windows and let Adaptive V-sync cap my framerates to my monitor's refresh rate. Because I have the game installed on an SSD, I didn't see an increased loading time after doing so! For anyone having abnormal amounts of tearing, please try removing this command from your "Game Properties" windows and report back with your results. You can also leave the cutscene framerate fix in there, since that still works fine without GameTime.MaxVariableFps. 

 

So Ive installed Windows 10 but unfortunately Im running into an issue with my phone preventing me from logging into Origin. Im hoping to get a code received soon but it may take until tomorrow before I finally get to test DAI on here. I had no problems installed Nvidia drivers or Origin though so that's a good sign.

 

Great job, Nauticle! Don't worry, there's no rush - just try DA:I on it whenever you have the time. I'm sure everyone here is very excited to read your results! 

 

Any way to make the world less "shinny" like disabling bloom or making metal armor/tacks/glass/hair/mustaches/belts/barrels/everything not shine so damn much???

 

I'm very sorry, but it seems there's no way to do that, unfortunately. The shininess of assets is not something that can be tweaked from either the in-game graphical settings or the console commands. If you do find a way to tweak it (maybe from the "ProfileOptions_profile" file?), then please report back and I'll update the OP as soon as possible! 

[Verrenus]

Updated the relevant section in the OP to point out that, based on my own experience, using the GameTime.MaxVariableFps command to cap your framerate can lead to excessive amounts of screen tearing for no apparent reason, even when setting it to the recommended value of 0.01 frames less than your actual refresh rate! 

 

If you have been using this command and were getting excessive screen tearing, then please try to remove it from your "Game Properties" window and use either the Frame Rate Limiter option in Nvidia Inspector or Adaptive/Regular V-sync to cap your framerate! Note that if you are using the cutscene framerate fix, GameTime.MaxSimFps and GameTime.ForceSimRate will still work fine without GameTime.MaxVariableFps, so you can leave the first two commands in your "Game Properties" window at their recommended floating values without any problems! 

[Nauticle]

Well with minimal tweaking/testing so far Windows 10 Technical Preview (build 9841) is a smashing success over Windows 7. Ill echo the statements made by Scooby in that the game just feels nicer even without constant 60fps. Like before Im testing in the area after the prologue/cutscenes and before talking to anybody.

 

Positives:

Performance. Im staying above 30fps at all times and can reach 60fps + quite easily. RAM usage seems to have dropped by quite a bit as well. CPU/GPU usage is roughly the same as before.

 

Stability. CPU and GPU graphs (in game) are a lot less radical in changes. They are also lower in general, have much better averages and the spikes that do happen are 50% - 75% of what they peaked at in Windows 7.

 

I have yet to test out any cutscenes so I can't comment on those yet.

 

Camera Movement is indeed much smoother as is character movement.

 

Negatives:

Screen flickering while any form of loading is happening that involves a loading screen.

Screen tearing is quite noticable and can be horrendous at times.

Artifacting seems to be limited to far off objects but isn't that common.

 

Questionable/Unrelated Comments:

Unfortunately Im unable to comment on load times as the drive being used for Windows 10 and DAI is not an SSD and not meant for performance at all.

Setting up the game and Origin to run isn't that difficult but can be a bit tedious (not so much on an SSD )

The camera movement feels very weird to me. It's hard to describe what exactly is the problem but it almost feels unnatural with how the images come into view.

 

My settings are on high quality except for the following. Running 1080p fullscreen @ 59.93hz Vsync (in game) enabled.

AO is set to SSAO

Tesselation is medium

Effects are medium

MSAA is off

Post Processing Effects? (DOF setting) is low

Post Processing AA is low.

 

user.cfg commands are

PerfOverlay.DrawFps 1
perfoverlay.drawgraph 1
WorldRender.MotionBlurEnable 0
RenderDevice.VSyncEnable 0
WorldRender.TransparencyShadowmapsEnable 1
WorldRender.LightTileCsPathEnable 1
RenderDevice.ForceRenderAheadLimit 3/4
RenderDevice.TripleBufferingEnable 0
Thread.ProcessorCount 8
Thread.MaxProcessorCount 8
Thread.MinFreeProcessorCount 0

 

Vsync was enabled during gameplay. My next test will be with the vsync/triple buffering commands enabled. I may also have redistributables to install/update.

 

 

TLDR: YAY.

 

Edit 1: So Ive spent some more time working with the Nvidia Control Panel, User.cfg and in game options/console commands to try and get a good balance between performance, tearing and hitching with regards to Vsync and Triple Buffering. It seems in-game options are total trash and wreck performance, don't do as good of job for tearing and has the least amount of hitching but its a more substantial spike. User.cfg seems sort of broken for some options and not others so it's hard to say. Nvidia Control panel does the best for tearing, moderate performance decrease (average 5fps Id guess) and has a more constant amount of hitching but quite a bit smaller spike wise. Tomorrow Ill probably create a graph for accuracy.

 

One more note is that cutscenes are not doing well regardless of the options. There is almost always a 5sec lag where the fps dips below 30 before returning at the beginning of one but it can happen randomly during one as well, the radial wheel/menu for dialogue can decrease fps by a large amount and tearing can be a issue even with vsync on. Im not sure whether its the HDD, CPU, Windows 10 TP, Nvidia or DAI that is the root cause for the issue and I doubt Ill be able to figure it out.

[Maria13]

The way I fixed my PC DA:I problem?

 

I got a PS4...

[Addai]

Hello Maria.

 

Still getting rampant DirectX CTD. Most annoying when it happens in the character creator, after I've got the character looking juuuust..... *crash*

[arkngt]

So do we have some kind of consensus on what causes these CTD issues on certain systems? I find it odd that the game runs perfectly stable for some and causes "rampant" CTDs for some. For me, it's very stable (two crashes in 170 hours) on Windows 8.1 with an ATI GPU.

[Crabby654]

So do we have some kind of consensus on what causes these CTD issues on certain systems? I find it odd that the game runs perfectly stable for some and causes "rampant" CTDs for some. For me, it's very stable (two crashes in 170 hours) on Windows 8.1 with an ATI GPU.

I think a lot of is the nvidia drivers for people with those cards. I have a 770 gtx and my first playthough was fine, second constant crashing so far. Its very bizarre.

[Verrenus]

Well with minimal tweaking/testing so far Windows 10 Technical Preview (build 9841) is a smashing success over Windows 7. Ill echo the statements made by Scooby in that the game just feels nicer even without constant 60fps. Like before Im testing in the area after the prologue/cutscenes and before talking to anybody.

 

Thanks a lot for taking the time to do this, Nauticle, your effort is much appreciated! 

 

I knew DA:I had to perform just as well on Windows 10 as it does on Windows 8.1, so I'm very happy to hear that still holds true, especially since this was only a technical preview! I'm sure that when Windows 10/DirectX 12/PCI Express 4.0 come out, we'll see another big jump in gaming performance on the PC. I for one can't wait!

 

As for your in-game experience, I would suggest forcing Adaptive V-sync in combination with the following "user.cfg" commands:

 

PerfOverlay.DrawFps 1

WorldRender.MotionBlurEnable 0

RenderDevice.TripleBufferingEnable 0

 

and these "Game Properties" commands":

 

-GameTime.MaxSimFps 59.92  -GameTime.ForceSimRate 59.92+

 

Furthermore, set Mouse Smoothing to the middle position (one notch to the right of the default setting) in the Controls menu in-game!

 

These should get rid of your screen tearing problems, as well as cutscene stuttering. Also, make sure to reinstall/repair all of the necessary redistributables, including the complete DirectX Runtime Library (June 2010). Great job once again though, gaming on Windows looks to be getting better and better! 

 

The way I fixed my PC DA:I problem?

 

I got a PS4...

 

Hey Maria! Not a bad solution, but one that I myself would never consider. Nevertheless, have lots of fun playing the game now! 

 

Hello Maria.

 

Still getting rampant DirectX CTD. Most annoying when it happens in the character creator, after I've got the character looking juuuust..... *crash*

So do we have some kind of consensus on what causes these CTD issues on certain systems? I find it odd that the game runs perfectly stable for some and causes "rampant" CTDs for some. For me, it's very stable (two crashes in 170 hours) on Windows 8.1 with an ATI GPU.

I think a lot of is the nvidia drivers for people with those cards. I have a 770 gtx and my first playthough was fine, second constant crashing so far. Its very bizarre.

 

I'm really sorry to hear you're having CTD problems guys!

 

I have never had the game crash on two different systems that I personally reinstalled Windows 8.1 and every other program and driver on. With the PC being such a complicated problem, I can only think of the reason being some underlying issues with the rigs that do not normally manifest outside of playing DA:I.

 

If you've reinstalled/repaired all of the redistributables, then I would suggest you look in your Event Viewer > Custom Views > Administrative Events and see all of the errors and warnings logged by your system. You can also use the Reliability Monitor to check out the same errors and warnings and from there to also search for possible solutions.

 

Please give this a go whenever DA:I crashes again for you, since there might be other problems that need to be fixed first in order for your game to run without a hitch! 

[Nauticle]

I thought Gametime Sim commands screwed around with load times, multiplayer and sound?

[Verrenus]

I thought Gametime Sim commands screwed around with load times, multiplayer and sound?

 

They do not screw up the loading times, nor the sound, but multiplayer is indeed affected by them, so bear in mind to remove them from your "Game Properties" window before playing any multiplayer matches. Alternatively, you can add the commands at the end of your DA:I shortcut path on your desktop, so that you will essentially have two shortcuts: one for singleplayer (with the cutscene fix commands) and a separate one for multiplayer (without the cutscene fix commands)! 

[Kurt M.]

However, Rubios noted that dropping Effects Quality below "Ultra" results in pixelated shaders, so try playing around with this setting to find out if the performance gain is worth the loss in fidelity!

 

That's odd. I've them in "Low", and I haven't noticed pixelation. They may be cheap, 'half-assed' effects, but not pixelated in any way...

[Crabby654]

Just as an obvious sidenote that I'm sure people know. I lowered my Ambient Occlusion from HBAO to SSAO and the FPS difference was insane, like I think a 20 FPS gain in Hinterlands.

[Verrenus]

That's odd. I've them in "Low", and I haven't noticed pixelation. They may be cheap, 'half-assed' effects, but not pixelated in any way...

 

Aww, crap, I think I know what's going on with the pixelation Rubios and I have been noticing. It must the same as with the grass shading artifacts, caused by HBAO, but not by SSAO or HBAO Full! 

 

Just to check, what ambient occlusion setting are you using in-game? 

 

Just as an obvious sidenote that I'm sure people know. I lowered my Ambient Occlusion from HBAO to SSAO and the FPS difference was insane, like I think a 20 FPS gain in Hinterlands.

 

HBAO is indeed very taxing in DA:I. While there is a visible difference between HBAO and SSAO, it's not that jarring and might prove to be a good compromise performance-wise. Did turning ambient occlusion down to SSAO really provide that much of a performance boost for your, Crabby? 

[Crabby654]

There was a lot less stuttering in Hinterlands for me, particularly around Dennets horse area. I need some form of ambient occlusion which is why I just set it to SSAO and not off and I am fairly happy with it right now. Ugh my poor 770 GTX chugs with this game! I cant wait to get a 970 later this year!

[Verrenus]

There was a lot less stuttering in Hinterlands for me, particularly around Dennets horse area. I need some form of ambient occlusion which is why I just set it to SSAO and not off and I am fairly happy with it right now. Ugh my poor 770 GTX chugs with this game! I cant wait to get a 970 later this year!

 

That seems to help a lot then, since I remember Dennet's horse farm being a particularly stuttery area as well! Of course, the game looks really poor without any sort of ambient occlusion, so SSAO seems to offer the best performance/image quality ratio. If only DA:I had Nvidia HBAO+, but sadly it's an AMD title. 

 

Anyway, if you are planning on upgrading your GPU I would suggest waiting until Nvidia brings out its 20 nm or even 16 nm chips this year. Sure, upgrading to a GTX 970 would give you a roughly 30% performance improvement, but with a 20/16 nm chip I wouldn't be surprised if the performance difference doubled! If you're really keen on upgrading your GPU, I would personally do it either before the end of the first half of 2015 and get a GTX 970 (my brother got a Gigabyte G1 Gaming model of that card and it's a magnificent piece of engineering!), or just wait a few more months after that and upgrade to a 20/16 nm chip model. 

[Kurt M.]

Aww, crap, I think I know what's going on with the pixelation Rubios and I have been noticing. It must the same as with the grass shading artifacts, caused by HBAO, but not by SSAO or HBAO Full! 

 

Just to check, what ambient occlusion setting are you using in-game? 

 

HBAO Full.

 

BTW, I don't know if I've gotten used to the low FPS and slowdowns or else, but I think that user.cfg tip with disabled motion blur and multithreading (4 CPU cores user here) has really stabilized my fps

 

So thanks! I'll draw a picture of a butt for you! (oh, Sera...).

[Verrenus]

HBAO Full.

 

BTW, I don't know if I've gotten used to the low FPS and slowdowns or else, but I think that user.cfg tip with disabled motion blur and multithreading (4 CPU cores user here) has really stabilized my fps

 

So thanks! I'll draw a picture of a butt for you! (oh, Sera...).

 

Thanks a lot for clarifying this! It seems normal HBAO is the culprit for pixelated effects, as well as cross-hatched grass. I'll try setting ambient occlusion to either HBAO Full or SSAO if the performance hit is too big. 

 

Heh, I'm really glad you've found this thread helpful and that you are enjoying the game now (a little too much maybe, but that's between you and Sera it seems)! 

[Black33]

HBAO Full here. No pixels in effects and the image quality is well beyond that of SSAO. What are your specs and settings on Nvidia Control Panel for Ambient Occlusion?

[Crabby654]

Out of curiosity does Ambient Occlusion (mainly HBAO Full) rely more on GPU memory or GPU speeds?

[Black33]

Out of curiosity does Ambient Occlusion (mainly HBAO Full) rely more on GPU memory or GPU speeds?

I've tried to find that info on nvidia's tech papers, hardware sites... nothing. I'd say it's speed related but the only way to make sure is to use Afterburner or GPU-Z and change the AO setting. Gonna try.

[Black33]

Ok, it seems to be GPU speed. Same save, same spot with HBAO and HBAO Full displays about 2-8% less GPU load on just HBAO. Memory usage is the same. The Hinterlands crossroads is a good place to measure if you're close to trees, grass and a fire. I must say I noticed HBAO to be too dimm. Trees and plants looked less vivid.