Turn 10 Studios and Microsoft have released a new update for Forza Motorsport 6: APEX. This new update brings various stability and performance improvements – especially for AMD devices – and adds an option via which players can disable VSync.
This update will be auto-downloaded from Windows 10 store, and you can read its complete changelog below.
Forza Motorsport 6: APEX – Update May 12th Changelog:
- Players can now disable Vsync in Apex (NOTE: This feature requires upgrading to a specific version of Windows 10 [OS Build 10586.318]).
- Stability and performance updates spanning a number of machine configurations, with specific focus on AMD devices
- Gameplay/objective modifications to a handful of events in both the Showcase Tour and Spotlight Series
- Improved integration between Apex and Forza Hub, as well as improved redemption flow for the free Nissan GT-R bonus car
- Additional UI fixes and general improvements, including: Expiration times for Spotlight Series events are now shown in local time; “New” UI designation now only applies to events that are actually new; Total medals available in Spotlight Series now only counts for active events
John is the founder and Editor in Chief at DSOGaming. He is a PC gaming fan and highly supports the modding and indie communities. Before creating DSOGaming, John worked on numerous gaming websites. While he is a die-hard PC gamer, his gaming roots can be found on consoles. John loved – and still does – the 16-bit consoles, and considers SNES to be one of the best consoles. Still, the PC platform won him over consoles. That was mainly due to 3DFX and its iconic dedicated 3D accelerator graphics card, Voodoo 2. John has also written a higher degree thesis on the “The Evolution of PC graphics cards.”
Contact: Email
DX12 games in general seem to be way more optimized for AMD hardware. Rain effects in Forza are very suspect. 390 has a 10/15fps lead over a 970 durring those effects. Like how 970 has a lead over the 390 in project cars.
You’re only just learning this?
No I been saying it since Mantle got dropped XD
Maybe 3.5 GB VRAM vs 8 GB VRAM has something to do with this, not to mention the 390 has more raw power than 970 anyway. Also Project Cars makes heavy use of Nvidia PhysX in its Engine so of course it will run badly on non Nvidia hardware.
Yes but the PhysX in Project CARS runs entirely on CPU as it’s CPU PhysX so shouldn’t be a concern of the GPU’s. I think it’s obvious why 390 has a 10fps lead when running at 2560x1440p and with 8xMSAA enabled as one card has a 256bit bus and the other a 512bit bus so bandwidth is an issue. Both cards cannot do 1440p with 8xMSAA @ 60fps anyway so it’s kind of like a hollow victory here as neither card manages 60fps at 8xMSAA. However both cards can do 1440p @ 60fps with 4xmsaa enabled. Or you could overclock the 970’s GDDR5 and core clocks for an easy 25% extra performance but the sane thing would be just dropping to 4xMSAA.
Project cars does not use Hardware PhysX accel. So not really. And the 3.5 gb is none sense. I go over it all the time and have no issues in single or SLI.
Also it’s just not 970 vs 390.. Fiji is beatsing 980 TI as well
isnt that the game where nvidia made it to where you couldnt turn off PhysX so they could screw over their competition i believe so.
You believe wrong. Again.
It did NOT make heavy use of PhysX. It was CPU based and a very cut down version that only took care of certain things in the game. The physics in the game was their own propriety engine.
amd made mantle which is similar to dx12.amd has worked with a low lvl api for years before dx12 launched.this is why nvidia struggles in dx12 they just stuck with dx11 and now they are making a big mistake trying to push vulkan.
dx12 is the gaming standard api right now and it mostly wil lstay that way.nvidia still has no async compute thats the big deal under dx12 and amd.
Please refrain from talking about things you know very little about.
lol i guess you shouldnt take about common sense then since you know very little about that.
It’s Hvd. What do you expect? Nothing but useless comments from him.
He’s totally clueless.
BIggest features of DX12 would be the Drawcall Overhead Redux and Low Level Hardware Abstraction in general (ASYNC can be a part of that). Async itself isn’t the biggest DX12 feature.
Nvidia can use Async compute just under lite loads. And we have not seen any games uses Async compute under lite loads. They are all heavy. And hitman is so heavy it effects AMD’s MAX fps on performance
What mistake oh clueless one? Pushing an open source multiplatform graphics API over a locked in proprietary one? OK, I’ve heard everything now. NVIDIA have always supported OpenGL well ,they even used it in their tech demos and linux drivers are very good, far, far better than AMD’s support of OpenGL on open sources OS’s.
BTW, AMD getting destroyed in Doom, GTX 970 is 4FPS behind a FuryX.
dont you remember this i have been posting everywhere on youtube and other sites btw thx..lol
only a 6fps difference in dx12 not vulkan…lol
, if you compare this to OC3D benchmarks, published on the 4th of April, you get this.
980Ti – DX12 -1440p/Crazy: 36.8
FuryX – DX12 -1440p/Crazy: 44.2
————————————————–GTX1080 – DX12 – 1440p/Crazy: 49.
remember this lol only a 6fps difference gtx 1080 and the older fury x.
oh btw as long a win 10 and dx12 are in the same os and dx12 is on xbox one it will be the industry standard api for gaming not vulkan..lol
You seem to be taking that benchmark of the GTX 1080 seriously and on drivers that are not mature or even released yet. Also, if this benchmark is accurate on unoptimised drivers, it would make the GTX 1080 over 30% faster than the GTX 980Ti anyway.
lol all you nvidia fanboys care about are your benchmarks when they favor you right?…lol 6fps difference.
and im making sure its known all over the internet.
Take them with a pitch of salt, the cards are not even out yet, the benchmarks were leaked, idiot.
me an idiot you were the one who leaked them and posted boasting the 30% boost the gtx gets over the 980ti.
hypocrite much?
“oh clueless one”
I laughed more than I should, thanks for that. xD
Right now Nvidia is doing better in Vulkan (Doom) so what you’re saying is not entirely true. Nvidia has weakness in Async workloads, not the entire API.
And AMD also doesn’t have some DX12 features like conservative raster, it’s just not heavily utilized at the moment and when it will then AMD will face problem. Both manufacturers don’t have full DX12 support but it’s going in AMD’s favor a bit more due to developers being more friendly towards consoles which has AMD.
“Right now Nvidia is doing better in Vulkan (Doom)”
How could you possibly even know that when there’s no AMD benchmarks for DOOM running on Vulkan?
It’s quite obvious because the Vulkan patch for Doom isn’t even out yet and they (ID) showcased it on a new GTX graphics card which means Nvidia and ID must be working on it from quite some time or they had some kind of collaboration.
AMD might show it on their new GPU launch but right now Nvidia is ahead of them in Vulkan support and most probably performance too. The game was running at 130 – 200 fps which means Nvidia must have good drivers as well.
Exactly so you can’t say Nvidia is doing better when you don’t even know how well AMD does.
That’s true though I hope AMD keep up this time because right now even their DX performance is not good.
Still, that’s just one example. Is like saying that Nvidia has better DX12 performance based only on Rise of the Tomb Raider. The difference here is that there are not other games that run on Vulkan to properly stablish a difference.
In case of Tomb Raider AMD said themselves that there are couple of issues which they will fix in their driver and things got much better after those drivers with CF scaling getting even better than SLI however in case of Doom, AMD did released day one driver and it’s still performing bad even in DX mode so there is something seriously wrong or simply lack of collaboration between AMD and ID.
I just hope they can provide better support for one of the most anticipated FPS right now, they first need to fix their DX issues and then they can see about Vulkan.
Most gamers and journalists usually stick to preliminary benchmarks so getting late means you’re out of game.
Oh, totally. But my point is that we can’t really say if Nvidia is better than AMD at Vulkan because A. there’s no AMD benchmark for Doom and B. there are no other games to see if it’s just matter of collaboration with one vendor or an API leveraging things one vendor offers but the other one doesn’t (for example: we can say it’s the former in the case of DX12 because of all of them that have been released, only one performs better on Nvidia hardware: RotTR, a Gameworks title).
But yeah, sadly we have to stick with day-one benches that doesn’t reflect the final state of the game. For example, I would like to buy Arkham Knight now that its price has dropped but I can’t find a performance status after the latest patches, which is frustrating. The guy from AdoredTV actually made a pretty cool video about that last week.
https://www.youtube.com/watch?v=BgaRDnyu5TU
AMD are getting totally wrecked in Doom, also, they seem to be using OpenGL 4.3 rather than 4.5, unless it’s a string error or something
We’re talking about Vulkan. Keep up.
You are speculating about it yes.
When R9 390 is performing much slower than 970 and 970 is reaching to Fury X levels then even a child can see that there is something wrong so please keep your fanboy comments to yourself.
There is no such thing as “full DX12 support”, so please stop saying it, GPUs manufactures pick from the tier support what they want, some of it is optional. This is why there has been so much bullsh*t about claiming NVIDIA not supporting DX12 fully because there is no such thing.
And there is no one stopping them from implementing as many tier levels as possible. If Nvidia will succeed in implementing a good preemption scheduler that can handle heavy asynchronous workloads then they’ll have the most broad range of DX12 features and they can go further as well so please stop saying something that you can’t prove.
The bullsh*t about Nvidia claiming full DX12 support came from journalists and Nvidia itself when they false advertised features they can’t provide, it has nothing to do with DX12 being divided in tiers, it was Nvidia who said first native DX12 architecture and it was AMD who cleared that up by saying there is no full DX12 support yet.
When I mentioned full DX12 support, I meant no one has clear advantage in DX12 right now except the fact that consoles have AMD which lead to more Async usage.
The stupid engine is limited to 60 fps. Hopefully one day I’ll be able to run it at 144 fps
I not hitting 144 but am above 60
The patch notes states:
[NOTE: As of this update, Forza Motorsport 6: Apex is still capped at a maximum frame rate of 60fps. The team is investigating adding support for higher framerates in a future update.]
I don’t know what to tell ya, I use dxtory to have an ingame fps counter and mid 70’s is what it says
I have overclocked 75Hz monitor and when i set dynamic framerate target i have 75 fps in race and 37 in menu.
What do they mean by “specific focus towards AMD devices” ? if Nvidia users are also facing some issues then they should fix them as well, biased attitude from developer is not good.
I think it may be that AMD devices where not getting as good performance as Nvidia originally. I can only speak for my self, but I get outstanding performance in this game w/ gtx 980. The only thing they can do is add more tracks and maybe VR mode
i can’t see any update for it
It is automatic, as long as you have the latest w10 build you’re okay.
i have the latest build!
aslo i am seeing in the game options !
60 FPS and 60 FPS V-SYNC wich one is the v-sync off?
aslo can i use adaptive v-sync from nvidia control panel?
Probably the one that doesn’t have “v-sync” attached to it…
got it
Choose the one that doesn’t state v-sync and yes you probably can use adaptive vsync, the goals of this update was to let it’s users use gsync/freesync.
thanks mate
I’m still getting a bit of stutter, but only at the beginning of my first race of each play session. After that, a solid 60 fps at all times. Very well done. A little more tweaking and we might have a winner.