It’d probably be better by virtue of not being an AMD card (nothing wrong with them, but Zwift runs on OpenGL for which AMD’s Windows drivers are… pants), but otherwise yes; you’d be massively CPU bound all the time on Neokyo with an i5-6600 anyway.
I don’t know. My I7-6700E is okay in Neokyo. The numbers aren’t great but it looks fine with no flicker or jitter. This was a pretty crowded event and I was in the pack until the last 10 minutes or so. The I5 might be okay…
That’s the whole point of the thread though, the numbers are far worse than all other worlds in the same circumstances. Even in that last 10mins you’re miles below 60fps, this wouldn’t be the case everywhere else*. P1 of 24fps is atrocious. 
*Well, before the last couple of updates…
I know a P1 of 24fps is amazingly bad considering the hardware. It doesn’t even get that bad in the Jungle Circuit dust. But, it doesn’t look that bad to me when I’m in there. Maybe there’s too much to see or something. I rode Neon Flats this morning and it was a very easy ride, testing out the sticky watts thing so I can’t say my vision was impaired by my physical effort. Just looked … fine. Not much different from anywhere else. I must be getting old or something…
Yeah, I was on a bit of budget at the time, less so now.
Just built a proper gaming rig with a 6700XT/5600X, but that PC lives in the house and this is in the shed.
What they actually did: make everywhere as bad as Makuri. 
2 Likes
Hmmm, this thread is depressing. I only started Zwifting around a fortnight ago, so I haven’t explored much at all. I’ve been running Zwift on the different PCs in the house, swapping components around to see what works out best, but I haven’t been to Makuri or Neokyo.
I’ve joined Dave’s excellent Zwift-build Facebook group and have been aiming at putting together a Frankenstein machine with old parts - which to be fair has been working okay, sans Makuri/Neokyo etc. - but now I’m wondering if I’ve wasted my time and I should really be looking at a new top end machine, considering future requirements (I know, there’s no future-proofing in PC gaming) in Zwift.
This is actually making me consider ditching Zwift altogether, I’m at the start of a free month but after that I’ll probably go Rouvy +/- TrainerRoad. Or just avoid the high-demand worlds.
What’s really laughable is that even in 4K/Ultra, Zwift still looks rubbish. It’s like looking at really old FIFA! The scenery’s better than the humans, but still…
I’m going for a ride this morning later on so I’ll try Makuri and Neokyo on my necro machine and see what happens. Hopefully they’re better with updates since April?
1 Like
It depends what your expectations are.
I use an old and underpowered mini PC or equally badly specd laptop and find all worlds are about the same as each other.
Frame rates aren’t great but perfectly fine for me. Graphics are also fine for me.
If you want super high frame rates and ultra graphics then speak to Dave about how best to do that but if you want an experience that works and looks alright you can get by on pretty low specd stuff.
I use 6th gen i3 pc I picked up for £40 and added a £20 SSD and it does the job for me.
1 Like
In fairness this thread hasn’t been updated since they changed the CPU behaviour to respond to threaded optimisation (ensure you follow the Nvidia settings guide on the group). Makuri is still significantly more CPU bound than all the other worlds, but it isn’t quite as bad as it was to begin with. The design in terms of foliage density is unchanged of course. There’s one particular spot in which I couldn’t hold 60fps with an RTX 2060 Super. 
Thanks for the kind comments.
Errr… Bump.
The threaded optimisation improvements appear to have been removed or rolled back. Makuri is horrifically CPU bound again, like it was at first release. Please resolve this.
1 Like
I’m back to barely staying over 60fps with 12th gen Intel in an event. Massive step backwards.
Yesterday my rig dropped to 90fps in this exact same circumstance, for less than five seconds, then it returned to 95fps capped. At least 50% better performance than just now.
Here’s yesterday: Zwiftalizer 2.0
Edit: unsure if this affects all worlds, not just Makuri. Doing more testing
Right so the other worlds are performing as normal (tested on both low and high end setups), and threaded optimisation still yields improved results on all worlds. So my theory about exactly what’s happened was wrong, but essentially on the latest 1.31.0 update with the new expansion included, frame rates on Makuri are significantly worse than 1.24.0 (13th April) through to 1.30.0.
12th gen Intel should still be fast enough to maintain 60fps in most scenarios (not a big/packed group ride), but anything older will see notably worse frame rates - particularly when it’s busy.
Please look into this. It’s especially disappointing given how attractive Urukazi is.
6 Likes
Happens on today’s tour ride…
Intel i5 7600k OC4.2
Nvidia 1080…
Never had frame drops before, even when using 4k tv and streaming using obs, today with 2k monitor and not a huge amount of riders i was constantly seeing frame drops…
I will test on watopia tomorrow…
1 Like
Zwift is using just one core of the CPU. Even if there are 6 or 8 cores. That’s the bottleneck.
Not quite, since April it’s used more than one thread. Also, I’m not saying the game isn’t still CPU bound a lot of the time - Makuri being worse than the others. I’m saying Makuri performs significantly worse now than it was on the previous update.
1 Like
i saw this last night, too.
running zwift at 1440 ultra, core i5 9th gen, GTX 1660 on a 60hz TV usually stays right around 60FPS, last night it was dipping into the 40s.
strangely, wed night when i first rode this updated makuri, i didn’t have this issue – it was only the second night.
1 Like
1 Like
same problem for me, mysteriously only in the old part of makuri and not on the new roads on the Makuri 40 lap