• Announcements

    • HEAVY265

      Attention Soldiers Operation Fury Needs you!   02/20/2020

      Attention All Soldiers, Operation Fury needs you.  You need to choose a side and sign up.  
      For more intel on Operation Fury Please click HERE Please go to Special Event Forum (here), And sign up for allied or axis.
      This will be a CRS Lead event on both sides.  Xoom will be heading up the axis side and Heavy265 will be heading up the Allied side. This will be for bragging rights.
      Why are we asking players to sign up you ask. We are trying for a role play experience.   We want this to be a true realistic event.  
      So get up and sign up and let's make this the best event ever!!!!!!!!!!
      Give me your war cry, grrrrrrrrrrrrr
      Heavy265 **out**
Sign in to follow this  
Followers 0
christianr

Can't enable or disable my effect settings..

17 posts in this topic

It sucks. The presets for best performance etc are locked in. I can't enable or disable them. Only under my effects tab though. Also, hovering over towns or people doesn't give me their names or what brigades are in that town. nothing serious but kind of annoying.

Share this post


Link to post
Share on other sites

I posted the same in the bug forums.. You can manually change your preferences in an XML file (iPhone won't let me paste :( ) ahwulf is trying to find a fix for it.. He can't replicate the issue

Share this post


Link to post
Share on other sites
It sucks. The presets for best performance etc are locked in. I can't enable or disable them. Only under my effects tab though. Also' date=' hovering over towns or people doesn't give me their names or what brigades are in that town. nothing serious but kind of annoying.[/quote']

Hovering is not a bug, its the Show Tooltips preference defaulting to off. Just turn it back on.

The effects prefs buttons are a complete mystery so far; nothing about them is wrong except they don't click.

Share this post


Link to post
Share on other sites

I think we are close to fixing this bizarroland bug. Apparently one of the labels is intent on taking over the world (ie covering the entire page).

Share this post


Link to post
Share on other sites

It will really help my performance when this is fixed. As of now i can't turn off the shaders or normal maps which are both known to not be so Mac friendly.

Share this post


Link to post
Share on other sites

Shaders and normal maps are very mac friendly in 1.31. In 1.30 they didn't work at all. Why not play with Best Performance in the meantime which works fine?

Share this post


Link to post
Share on other sites

Hi all,

I too would like to know what to do to get the best play out of my system. I have been running 2500 x 1400 with balanced setting, but I die with every close encounter it seems. Now I'm trying 1900 x 1200 with the performance setting.

However, I would like to run at the higher res with the balanced or best quality and keep descent FPS. (ok, I wan't both, fast play and graphics ! )

With these state of the art computers (quad core, nice video) we should be able to have both... yes?

Share this post


Link to post
Share on other sites

What do you have?

What do you mean die - in game or crash?

I have a MacPro/2.66 i7 with ATI 4870 and run a modified debug version, most of the time I'm at 20-60 fps (Vsync) and quite steady with everything on at 1920x1200. In the worst battles I might drop into the teens on occasion but its rarely an issue.

Share this post


Link to post
Share on other sites

I have a brand new quad core imac 27", great computer, FPS is always good.

But, as I've posted in barracks, something is wrong, game play completely sucks now. Terrible lag, I die almost every time in a depot battle. This never happened in 1.30

I keep hearing about predictor code, what is it? Why has suddenly I always die and there is such big lag and I don't even KILL the guy? I almost always get the first shot off, he doesn't die, he turns and kills me, and half the time I don't even hit him at all? Something is very wrong.

Share this post


Link to post
Share on other sites

Your internet connection may be to blame. If you can. run Terminal (/Applications/Utilities I think). Type in

traceroute 66.28.224.230

you should get something like

traceroute to 66.28.224.230 (66.28.224.230), 64 hops max, 52 byte packets

1 192.168.1.1 (192.168.1.1) 0.829 ms 0.611 ms 0.591 ms

2 10.0.XX.XX (10.0.XX.XX) 8.547 ms 7.470 ms 7.473 ms

3 24.164.210.164 (24.164.210.164) 8.500 ms 8.043 ms 7.479 ms

4 24.164.208.182 (24.164.208.182) 7.970 ms 9.266 ms 7.910 ms

5 70.125.217.76 (70.125.217.76) 9.479 ms 10.046 ms 9.456 ms

6 gig2-0-3.hstntxl3-rtr1.texas.rr.com (72.179.205.46) 14.397 ms 142.323 ms 30.028 ms

7 ae-2-0.cr0.hou30.tbone.rr.com (66.109.6.108) 13.979 ms 14.648 ms 14.064 ms

8 ae-0-0.pr0.dfw10.tbone.rr.com (66.109.6.181) 18.401 ms 18.639 ms 19.038 ms

9 te9-4.mpd01.dfw03.atlas.cogentco.com (154.54.11.49) 18.468 ms 18.051 ms 18.030 ms

10 te7-1.ccr02.dfw03.atlas.cogentco.com (154.54.25.6) 19.541 ms

te8-1.ccr02.dfw03.atlas.cogentco.com (154.54.25.10) 18.627 ms

te2-4.mpd01.dfw01.atlas.cogentco.com (154.54.6.65) 85.650 ms

11 te8-1.ccr02.dfw01.atlas.cogentco.com (154.54.7.254) 19.070 ms

te7-1.ccr02.dfw01.atlas.cogentco.com (154.54.7.250) 21.069 ms

te8-1.ccr02.dfw01.atlas.cogentco.com (154.54.7.254) 19.120 ms

12 te4-2.ccr01.dfw02.atlas.cogentco.com (154.54.26.162) 19.412 ms 18.655 ms 19.973 ms

13 playnet.demarc.cogentco.com (66.28.30.146) 20.074 ms 19.578 ms 19.541 ms

14 * * *

control-c to quit

The first couple might be all * * * depending on your ISP. Paste your result here.

Did you try using netcode2 (or not using it if you are) (ingame preferences)? Have you tried changing the game laucher Settings:Connection to Primary or Secondary (instead of Best). These things will change how packets get to and from your computer. I also assume you are not running on a dialup still?

Share this post


Link to post
Share on other sites

Hi there,

traceroute to 66.28.224.230 (66.28.224.230), 64 hops max, 52 byte packets

1 192.168.0.1 (192.168.0.1) 1.852 ms 1.495 ms 1.575 ms

2 gateway.netzero.net (192.168.1.254) 2.224 ms 2.899 ms 2.170 ms

3 10.35.91.1 (10.35.91.1) 33.410 ms 32.856 ms 31.492 ms

4 p0-3.plspca-lcr-01.verizon-gni.net (130.81.34.208) 31.524 ms 34.680 ms 31.429 ms

5 so-0-3-0-0.lax01-bb-rtr1.verizon-gni.net (130.81.22.52) 35.572 ms 36.391 ms 37.453 ms

6 0.so-6-3-0.xl3.lax15.alter.net (152.63.113.241) 37.417 ms 36.511 ms 37.602 ms

7 0.ae3.br3.lax15.alter.net (152.63.113.185) 35.397 ms 39.163 ms 38.956 ms

8 te7-2.ccr02.lax05.atlas.cogentco.com (154.54.13.85) 35.375 ms 38.510 ms 35.231 ms

9 te2-6.ccr01.lax01.atlas.cogentco.com (154.54.30.197) 92.667 ms

te7-4.ccr01.lax01.atlas.cogentco.com (154.54.3.9) 78.074 ms

te3-8.ccr02.lax01.atlas.cogentco.com (130.117.50.89) 38.701 ms

10 te9-8.ccr02.iah01.atlas.cogentco.com (154.54.3.185) 77.789 ms

te3-8.ccr01.iah01.atlas.cogentco.com (154.54.0.226) 78.153 ms

te9-7.ccr01.iah01.atlas.cogentco.com (154.54.0.234) 76.159 ms

11 te4-2.ccr02.dfw01.atlas.cogentco.com (154.54.25.213) 78.229 ms

te8-3.ccr02.dfw01.atlas.cogentco.com (154.54.1.73) 75.522 ms

te4-2.ccr02.dfw01.atlas.cogentco.com (154.54.25.213) 77.866 ms

12 te4-4.ccr01.dfw02.atlas.cogentco.com (154.54.26.34) 77.760 ms 77.892 ms 76.957 ms

13 playnet.demarc.cogentco.com (66.28.30.146) 78.667 ms 81.725 ms 78.736 ms

14 *^C

But, nothing has changed on my end since 1.31 came out (well, that I'm aware of) It's not lag, as in slow screen updates, its that I shoot him and he doesn't get shot, but knows to turn and shoot me.

Share this post


Link to post
Share on other sites

Hmm, that looks fine. In infantry preferences, do you have all 4 of the settings enabled?

The way the game works is, shots you make are generated on your client, shots others make are generated on their client, then the result is sent to each other. So if you shoot someone and they die, by the time the packets go to and fro its possible for them to shoot you as well. You can't help internet lag; how long it is depends on how far apart the two of you are from the server. However if you register a kill on your end he will die, but he might not be notified for a couple hundred milliseconds or more.

Generally in 1.31 when you hit someone you see blood (if its on). Of course hitting someone is not always going to kill them.

The thing to do to investigate further is to get a buddy on the training server and shoot him and vice versa, to see if anything is really wrong. I can't imagine any way for just one client to be unable to kill anything without it happening to other people as well - but if it was happening it might be some combo of preferences that is broken.

Share this post


Link to post
Share on other sites

A number of PC players are reporting the same thing - can't kill people inside certain buildings. I still wonder if its a combo of infantry pref settings.

Share this post


Link to post
Share on other sites

I used the balanced setting, so what ever it defaults to. I think 3 of the 4 are on, but no rag doll weapons.

Share this post


Link to post
Share on other sites

It never happens to me - just for fun try playing at both highest performance and then whatever the everything is on setting is called. Also try turning off or on netcode 2. If it still happens then at least it rules out one possibility.

Share this post


Link to post
Share on other sites
Shaders and normal maps are very mac friendly in 1.31. In 1.30 they didn't work at all. Why not play with Best Performance in the meantime which works fine?

Hi Ahwulf,

I'm glad that they are working with Mac now. However the water reflections to me look like 8 bit Nintendo graphics on my system and I am getting only 4-6 FPS for the most part as inf. About 10 FPS is as good as I get as inf at max settings. I thought I had a decent system..... Maybe not, You tell me (please).

I am playing at 1920X1280 and have experimented with turning the clutter all the way down to no avail.

21.5 inch Imac (Newest Generation)

Snow leopard 10.6.3

3.06 Intel core duo

4 GB of Ram

NVIDIA GeForce 9400

256 Mb of Ram

Thanks for the help,

Parra00

Share this post


Link to post
Share on other sites

Its fine except the 9400M is the raw bottom of possible; that's one of the two (other was 2600HD) I thought were not even going to be playable at all.

To make it run acceptable you need to accept Best Performance Setting and even lower the resolution to 12xx or something. The 9400M is very sluggish and with only 256MB vram its breathing hard on all those pixels and options. I wish @#$@# Apple had made the video card upgradable to anything.

You can play with that card but you have to reduce the things that cause it to choke. Best to start at Best Performance, 12xx resolution, no FSAA. Then add features to see what affect they have. This will of course be easier when I get with Ramp and fix the checkbox bug. If you can play at base minimal settings then we can see how many features we can turn on.

I have a wimpier iMac at work with a similar lame video card but its playable if you don't push it too much. Offline at 1280 and best performance I am seeing 60+fps.

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.