• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Fallout 4 to feature Nvidia Gameworks

nashathedog said:
Out of interest what is that?
It sounds like something you need to mod or do via a console command not a menu setting.





I think it's more that people expect 4 or 5 hundred pound graphics card to be able to run something like that on it's highest settings a lot better than it does.

How much better does Fallout 4 really look on PC over console?
We are told that the PC's we spend 3 or 4 times more on are that many times more powerful than consoles but we get a negligible visual improvement that put's performance in the gutter.

I look at games like Alien Isolation and see these effects running while my fps is sitting close to triple figures.


http://i1-news.softpedia-static.com...quel-Ideas-Won-t-Focus-on-Action-467332-4.jpg


http://www.psmania.net/wp-content/uploads/2015/02/15103768993_64e1e8dae7_k.jpg
Even modded to max it out the hit is smaller than what we are getting given by AAA dev's lately.
Click to expand...

My understanding is that uGrids is a config setting you need to edit an ini for or possibly use the console. I believe it basically decides how far around you get rendered in full detail. So with 5 you get stuff rendered if it's close but things on the other side of the water would have reduced detail. If you turn it up to 7 it will fully render things in the water, 11 would render building sat just on the other side of the water and 13 would do things a distance the other side of the water. There was actually a good example on Nvidia's Tweak guide.
In fairness Nvidia's Tweak guide made quite clear the performance hit that you'd get from these effects. Not sure why they took it down.

I agree that it's silly including effects that even on Nvidia's graphs show they will impact fps to an almost unplayable level (depending on the person I guess). Maybe if the game supported multi-gpus there'd be a reason to have it. Give those people a little something to do with all the extra power they had. Still I think multi-gpu is a Bethesda issue.

I remember the first Rome: Total War had some settings to do with unit size (I think) that determined how many units were rendered on screen in the battle mode that had settings allowing you to set it higher than current GPUs could manage and they said that it was to future-proof for new hardware (think it was in a tool-tip for the setting). I thought at the time it was a bit silly and ambitious planning that far ahead. Of course seeing how Creative Assembly's Total War games have gone on it now seems like that could've been an excuse!

Remember that the console version runs at 1080p 30fps with common dips into the 20s and on the XBOX occasional stutters where the fps hits 0.
 
muziqaz said:
Did anyone looked into performance of faster ram? one of the review sites done some testing with 1333Mhz ram and 2400Mhz ones, and jump in performance was quite noticeable. Cannot remember the site name, though.
Click to expand...

Saw that article and it works in Skyrim too. Its nice to have 2400mhz ram but didn't think I'd see a noticeable performance increase with it.
 
muziqaz said:
Look, your argument is that 980ti has more fps and thus loses more due to percentages. I get it, but, how does your percentage argument works with Titan X and now Fury X with new drivers? With old drivers fury x lost around 30FPS, with new drivers it still loses around 30fps even though now Fury X has much more fps to lose.
Click to expand...

It's not a 'percentages argument'. That's just how you compare.
 
muziqaz said:
Yes, you can compare when comparisons are consistent. In this case these comparisons fly out of the window ;)
Click to expand...

Err, no they don't for the reasons outlined in my initial post.

The driver thing is irrelevant. It just means that AMD have improved their driver. It has no relevance to whether to compare via percentages or not. You always do as it maintains relevance to the two data sources.
 
Rusty0611 said:
Err, no they don't for the reasons outlined in my initial post.

The driver thing is irrelevant. It just means that AMD have improved their driver. It has no relevance to whether to compare via percentages or not. You always do as it maintains relevance to the two data sources.
Click to expand...

Ok, did percentage change when AMD increased performance of their cards?
Do your little exercise with %s now, PLEASE.
How come AMD can improve drivers for 1080p and 1440p and 4k, while nvidia does just for 1080p an their quality of drivers fall off with higher resolutions?
 
muziqaz said:
Ok, did percentage change when AMD increased performance of their cards?
Do your little exercise with %s now, PLEASE.
How come AMD can improve drivers for 1080p and 1440p and 4k, while nvidia does just for 1080p an their quality of drivers fall off with higher resolutions?
Click to expand...

Because perhaps AMDs drivers were worse in this game from day 1 and when they had proper access to the code they could improve things more? It isn't difficult to comprehend. That doesn't change the basis of why you compare in percentages and not actual FPS figures.

I give up you just don't get it so it's futile to try and make you understand.
 
Rusty0611 said:
Because perhaps AMDs drivers were worse in this game from day 1 and when they had proper access to the code they could improve things more? It isn't difficult to comprehend. That doesn't change the basis of why you compare in percentages and not actual FPS figures.

I give up you just don't get it so it's futile to try and make you understand.
Click to expand...

You do realise that I never disputed the usage of % in comparison. But in this case your usage of % and your argued point does not work.
Originally it was argued that nvidia and amd lose the same amount of performance with change of resolution. Yes? Yes. My point of view was that %s in this case DO NOT tell you the whole picture between architectures and GPU scaling. I know that fiji is better suited for higher resolutions, and that was my point, that when you go up in resolution, fiji will always lose less performance be it with %s or FPS. Yet the argument continued.
Now we have optimised drivers from AMD, and fiji again is confirming my previous observations, that it is much better handling higher resolutions.
 
muziqaz said:
You do realise that I never disputed the usage of % in comparison. But in this case your usage of % and your argued point does not work.
Originally it was argued that nvidia and amd lose the same amount of performance with change of resolution. Yes? Yes. My point of view was that %s in this case DO NOT tell you the whole picture between architectures and GPU scaling. I know that fiji is better suited for higher resolutions, and that was my point, that when you go up in resolution, fiji will always lose less performance be it with %s or FPS. Yet the argument continued.
Now we have optimised drivers from AMD, and fiji again is confirming my previous observations, that it is much better handling higher resolutions.
Click to expand...

That isn't what you said at all but OK. As I said I give up with you.
 
Klunt Bumskrint said:
Kind of, we got an SLI profile which works ok most of the time. There are parts of the map where my gpu usage plummets to 30-40%
Click to expand...

I dont think thats due to the SLI profile not working but more a game issue. Shadows can tank my fps in certain areas for no reason at all causing GPU usage on my single 980ti to drop a fair bit.
 
Fallout 4 Update Adds HBAO+, NVIDIA-Only Weapon Debris Effects

Bethesda has just posted the changelog for the latest Fallout 4 update (1.3), and there’s quite a few interesting items in the list.
For instance, there is now a new ambient occlusion setting for HBAO+ (the technology developed by NVIDIA which is however available on AMD cards as well). Moreover, Bethesda added new weapon debris effects in this Fallout 4 update and specified that these will be NVIDIA only. It seems likely that they are based on NVIDIA’s PhysX, though there is no such official confirmation yet; we’ll update this story once we have screenshots and/or videos of the new effects.
Keep in mind that this is a beta update, so you’ll have to follow this procedure in order to try it right now, and the developer also recommends to back up any saves before trying it.

  1. Log into Steam
  2. Right Click on Fallout 4 in your Library
  3. Select Settings
  4. Select Betas
  5. A drop down menu will appear. Select Beta Update
  6. Select OK.
  7. Wait a few minutes and Fallout 4 should update.
  8. When done, Fallout 4 should appear as Fallout 4 [beta] in your Library

Good stuff and extra bits for Nvidia users.
Read more: http://wccftech.com/fallout-4-update-adds-hbao-nvidiaonly-weapon-debris-effects/#ixzz3xKgLwvWE

New Features
New ambient occlusion setting, HBAO+
New weapon debris effects (NVIDIA cards only)
Added status menu for settlers in your settlements
Added ability to rotate an object you are holding with left/right triggers and pressing down on left thumbstick lets you switch the rotating axis
Improved “ESDF” keys remapping support while in Workshop mode

Gameplay Fixes

  • General memory and stability improvements
  • Improved performance when looking through a scope
  • Fixed issue where player could warp to a different location when aiming
  • Companions can no longer get stuck with radiation poisoning
  • Fixed an issue where Vault 81 residents would not dismember correctly
  • Big Leagues perk now displays calculated damage correctly
  • Fixed issue with third person camera not displaying properly after exiting certain crafting stations
  • Fixed an issue where subtitles would occasionally not update properly
  • Effects will properly be removed on companions when items are unequipped
  • MacReady’s Killshot perk now calculates headshot percentages properly
  • Fixed an issue with NPCs getting stuck in Power Armor
  • Fixed a rare issue with companions getting stuck in down state
  • Second rank of Aquaboy now calculates properly
  • Fixed an issue with resistance not always lowering the damage correctly when added by mods
  • Enabled number of characters available when renaming an item (XB1)
  • Fixed issue with player becoming dismembered while still alive
  • Robotics expert is now usable in combat
  • Stimpaks can now be used on Curie after the transformation
  • Playing a holotape found in wilderness while switching point of view no longer causes the screen to blur or controls to be locked

Quest Fixes

  • Fixed an issue with “Taking Independence” where the minutemen remaining from the battle against the Mirelurk Queen would not gather in the Castle
  • Fixed an issue where invulnerable characters would get stuck in combat
  • Fixed an issue where Preston would send player to a settlement instead of a dungeon as part of a Minutemen quest
  • Fixed an issue where Synths could attack the Castle while the player was friends with the Institute
  • Fixed an issue where killing a caravan would leave a quest open
  • Fixed an issue where Dogmeat would stay at Fort Hagen after “Reunions” was completed
  • Fixed an issue where the player couldn’t talk to Desdemona to complete “Underground Undercover”
  • Fixed an issue where the player could get stuck exiting the cryopod
  • Fixed an issue where the player could no longer get Preston as a companion
  • In “The End of the Line,” fixed an issue that would prevent the player from killing the leaders of the Railroad
  • Fixed an issue with Minutemen quests repeating improperly
  • Fixed an issue where the player couldn’t get back into the Railroad headquarters after being kicked out of the Brotherhood of Steel
  • After finishing “The Big Dig,” fixed an issue where Hancock would no longer offer to be a companion or help with the “Silver Shroud” quest
  • Fixed an issue with obtaining the Dampening Coils from Saugus Ironworks before going to Yangtze
  • During “Unlikely Valentine,” fixed an issue where the player could be blocked from entering Vault 114
  • In “Confidence Man,” Bull and Gouger can now be killed
  • During “Taking Independence,” fixed an issue that would prevent the radio transmitter from powering up
  • In “Human Error,” fixed an issue where killing Dan would cause the quest to not complete properly
  • Fixed an issue with “Tactical Thinking” where leaving dialogue early with Captain Kells to reprogram P.A.M. could cause quest to not completely properly

Workshop Fixes

  • Fixed a bug that would cause settler counts to appear incorrectly
  • Fixed an issue that could prevent the player from setting up a supply line in settlements with a high population
  • Improvements to snapping pieces together while in Workshop mode
  • Fixed an issue that caused powered items to stop functioning permanently if its power source was ever removed
  • Player can now build workbenches in their Diamond City house
  • Building wires no longer uses up copper
  • Fixed issue with certain settlement attacks not generating properly
  • Fixed an issue with settlement happiness calculations
  • Settlers assigned to weapons stand will now stand next to it
  • Diamond City house now shows provided power
  • Repairing items will now correctly consume resources
  • Fixed an issue where companion would ignore commands at workshop locations
  • Fixed an issue with crops appearing destroyed after saving and reloading
Click to expand...
 
Last edited:
Makes no difference to me. I'm already done with the disappointment known as Fallout 4. A heavily nVidian title going more nVidian isn't all that much of a surprise either. *shrug*
 
You must log in or register to reply here.
Back
Top Bottom