9 replies to this topic

[LordBraxton]

In CB I ran this game smoothly until the cicada patch came out and broke the optimization for me, simultaneously making the game look and run much more poorly. I am not alone in having these issues.

My only real beef with PGI is that I was invited to the CB for free, and offered a look at an *unfinished product that I could invest in. Luckily I only gambled $30 so no big loss.

I am a little upset though that after being tempted in with a FREE product and purchasing, the game changed drastically and became unplayable for me, rendering my small investment of money and large investment of time pointless.

TLDR

My real question is to the code monkeys in the community, what kind of changes in these recent patches can make a game that looked so good 2 months ago look worse on my friends gaming rig and run worse on my budget pc at the same time?

[Fajther]

I too had lots of problems since that patch, but mostly to do with my wifi card. I know now that if I want to play the game i need to use a cable. It would be nice to know what they did on that patch.

[LordBraxton]

Fajther, on 26 November 2012 - 02:49 PM, said:

I too had lots of problems since that patch, but mostly to do with my wifi card. I know now that if I want to play the game i need to use a cable. It would be nice to know what they did on that patch.

I use wifi so I will have to try this to see if it helps with enemy rubber banding etc, if only I could get my old framerate back though!

[Vlad Ward]

LordBraxton, on 26 November 2012 - 02:45 PM, said:

My real question is to the code monkeys in the community, what kind of changes in these recent patches can make a game that looked so good 2 months ago look worse on my friends gaming rig and run worse on my budget pc at the same time?

Updating to Cryengine 3.4 without adding DirectX 11 support, for starters.

We actually had DX11 unlocked a couple months ago during closed beta, but they found a couple major issues with the implementation and patched it out until they could get it working properly.

[Dakkath]

LordBraxton, on 26 November 2012 - 02:45 PM, said:

In CB I ran this game smoothly until the cicada patch came out and broke the optimization for me, simultaneously making the game look and run much more poorly. I am not alone in having these issues.

My only real beef with PGI is that I was invited to the CB for free, and offered a look at an *unfinished product that I could invest in. Luckily I only gambled $30 so no big loss.

I am a little upset though that after being tempted in with a FREE product and purchasing, the game changed drastically and became unplayable for me, rendering my small investment of money and large investment of time pointless.

TLDR

My real question is to the code monkeys in the community, what kind of changes in these recent patches can make a game that looked so good 2 months ago look worse on my friends gaming rig and run worse on my budget pc at the same time?

I know this is kind of grasping at straws here but can you do the following:

- Update all DirectX9 components
- Update your video card drivers
- Update your .NET builds
- Uninstall the game / Remove the previous folder/data / Reinstall
- In game settings (Turn off Anti-Aliasing, and Post Processing)

If you have an NVIDIA card, turn off the Ambient Occlusion from both the General and Game Specific profile.

Hope that helps.

[LordBraxton]

Vlad Ward, on 26 November 2012 - 03:00 PM, said:

Updating to Cryengine 3.4 without adding DirectX 11 support, for starters.

We actually had DX11 unlocked a couple months ago during closed beta, but they found a couple major issues with the implementation and patched it out until they could get it working properly.

Well that explains why it looks worse on my friends gaming rig!

[ciller]

My suggestion to you is wait for a few more patch cycles and see if they can get proper directx implementation into the game. It might smooth things out.

Its too bad you can't make it run well. I had to turn down some of my settings since the cicada patch (when they added fancier stuff to the maps) to get proper frame rate.

[Blark]

I've noticed a major drop in performance too (i5-2500k@4ghz, gfx570).. its not that bad for me, I went from 50-60fps to 25-60fps.

What I find curious however is the extreme cpu load I get sometimes while my gpu is only at 60-70%; the only other game I played that was so cpu hungry was apb (100people+cars, npc's and complex customization), so I wonder where the high cpu load is coming from.. didn't notice it before the fps went down.

[TigrisMorte]

LordBraxton, on 26 November 2012 - 02:45 PM, said:

...
TLDR

My real question is to the code monkeys in the community, what kind of changes in these recent patches can make a game that looked so good 2 months ago look worse on my friends gaming rig and run worse on my budget pc at the same time?

check the similarities. ISP? GPU maker? OS? memory? fragmentation? nationality? star sign?
Something in there does not like the code. Since they have not implemented detailed fine tuning you can't remove shadows, shading, lighting modes, or whatever that are not "favored" by whatever it is.
Until fine tuning is in you can either wait and hope or play with the cfg and hope they don't declare that a cheat.

Trust, they do know the outcome of their changes, they have metrics. They are working to resolve this but...

[PapaKilo]

Vlad Ward, on 26 November 2012 - 03:00 PM, said:

Updating to Cryengine 3.4 without adding DirectX 11 support, for starters.

We actually had DX11 unlocked a couple months ago during closed beta, but they found a couple major issues with the implementation and patched it out until they could get it working properly.

This is incorrect.

Before they upgraded to CryEngine3 version 3.41, there was no DirectX 11 version (previous versions couldn't do DX11 at all, according to the devs). After they upgraded to version 3.41, there STILL was no DirectX 11 version available to us, as they found problems with their internal testing of the implementation. They will eventually get the problems fixed and release to us a DX11-enabled version, but it may take a while.

Edited by PapaKilo, 26 November 2012 - 08:47 PM.