You are not logged in.
I agree that 2 points for a flag and 1 for a kill is fair. "Otherwise you can end up with the top player winning it for his team" This is the point of the round. Winning for one's team. Kills are nice to have but they don't win the round, Flags do.
There was a BFsoldier_# on Tanks-A-Lot a few days ago shooting friendly vehicles. I tried banning him but he immediately returned and started SFVs again. I had to sit in one home base typing out the ban commands over and over for 20-30 minutes just to protect the actual players. Unfortunately, this guy has some way around the bans that keeps any ban from being permanent. My guess is this is the same guy. He's evaded so many bans once he's identified he'll be perm banned for all eternity...
shhhhhhhhhhhhh...
TGA is an unfortunate format for BF42 to save it's screenshots. I always have to convert the files when I want to use them in anything else. Picasa on my machine(s) won't even list a TGA file in spite of Picasa Photo Viewer having no problem with that format.
I still use Picasa to organize and display my photos, except if they're TGA...:-(
I think I see why 11 wasn't a choice. I didn't check how old this question was before answering...
I use a Windows 11 machine when playing. Why was 11 not among the choices?
At least you got it going. I have had it lock up so that task manager never displays too. Sometimes it works sometimes it doesn't
Maybe setting Blackscreen.exe to run as administrator. I don't really know what's going on there but that step is also commonly suggested to get it to run. I've never seen the black border situation.
Also, you can get out of the hung game using CTRL-Alt-Delete and end task in task manager. Doesn't solve the root problem but that usually works for me to kill it when my game goes into frozen-can't-change-kit mode Good luck. People have asked me several times if you've been banned. For what it's worth I'm glad that's not the case.
I was unable to play for 2 weeks while I was out of town and when I returned I find that it is now possible to TK my team mates on a server where this was not the case for so many years. Please reset the server to the way it has always been. Changing this setting will alter the entire character of play on Tanks a lot. With the TK being on, the only remaining all Aberdeen server will go back to the wild west-like conditions of the past.
I see constant complaints on the forum about being banned for "Killing a TKer??? How unfair!"
This has not been at all common on Tanks a Lot. It wasn't a problem and didn't need "fixing". If this is experimental like the changes made to the main server, then this is my vote against it. It will simply disrupt the smooth play we've long had. Historically there have been too few or no admins available on Tanks A Lot like there are on the main server. This has been a little better lately as there have been more admins playing there regularly, but still not enough. I am still often the only admin there. Please give us back our peace in the war zone.
I did check my scores for a few days after reading ironfarts kills only comment on gametracker and that appeared to be true. I also tried playing without using my “antifreeze” and my game hasn’t frozen either for a few days. Maybe it’s fixed?
If so that’s great but now I’ll be away from the game for a couple weeks and can’t test it again until I return from my 4th trip to Seattle. At least I will be able to return soon instead of the 2 periods of 8 weeks away last year. Withdrawal symptoms will minimized…
Score is misleading on Gametracker. It should be labeled, Kills then. I'll continue to play for team victory. Kills or Captures I'll continue doing whichever I think helps my team the most. It might very well encourage spawn camping for some, though.
I'll keep an eye on this when I play again. If it is only kills that it tracks, I'm screwed :-)
WTF Gametracker!
I think its relevant to this post.
Being an 'average' player little victories are important to me.
Gametracker having reset their statistics have regained a new vigour for some people to top the lists and why not?Imagine my chagrin to realise my stats have been nullified by whatever...
Gametracker claims that I played for 3 1/2 hours scoring 0 when I actually played for 20 minutes yesterday scoring something dunno what.
Left abruptly due to hopeless stacking btw.I was quite proud of my scoring ratio but that's f****d now.
I've noticed this before many times but always put it down to my VPN confusing things.
However I'm fortunate not to need it any more due to good connection for a month now.
It also happened to Test01 I've noticed but nobody else!I guess its no big deal but I've found it discouraging.
Hope nobody else feels the same.
?
Since the Gametracker reset I have been trying to keep track of my scores. Days when I've had over 100 points, gametracker reports less than 50. I see it doing the same thing to others who I know had higher scores than I did. It definitely has problems, probably all along.
Yes, Sepp is OUR sepp and he provides a lot of amusement. It does take 3 "bad" words to get him autokicked, BTW but he's dependable in that way.
That video is hilarious. Especially to those of us who've played all these scenarios.
Thanks for the suggestions but the problem is solved. Call it a PEBKAC error. I'm up and running now.
Apologies for the length of this post:
I have a new PC running Windows 11 on which I've been able to get BF42 running but the display is a mess. This was installed from the "Complete Collection" disks and patched to 1.62 and the newest gamespy replacement patch (from Henk).
System:
Gigabyte Z790 AORUS ELITE AX 32G RAM
NVidia GeForce RTX 3070 8G on board
Bright white rectangles show at the top and bottom of the screen. They cover up the menus so I can't select any settings. The list of servers shows the available servers but there is no highlighting of a selection. I can double click on the servers with players but once the game is running I can't double click a spawn point and the list of kits won't allow me to change them. I can select a spawn point by holding the mouse cursor over the choice and hitting Enter but when I spawn, none of the controls work. Or I don't spawn at all and the intro screen for the map continues to show. I can choose a local game but can't actually start to play. It's unplayable.
The app is set to run as administrator and the compatibility mode is set to Windows XP Service pack 3. I ran the compatibility troubleshooter but it sets the mode for the same as above.
On my Windows 10 machine the path to the working version of BF42 is
"C:\Program Files (x86)\EA GAMES\Battlefield 1942\" (same as my Win 11 machine)
The Bf1942.exe file is set to run in compatibility mode, Windows XP sp3
The properties of the compatibility settings are set to use the above with "run as administrator" checked but grayed out so they must be set elsewhere?
I appear to have directx 9 installed (d3dx9 dlls in both system 32 and sysWOW64)
I've tried running dxdiag which generates a large report but I'm not sure if that will even help to get BF42 running, but the report is available if anyone would like to see it.
I hope someone can resolve this. I got the new machine because the WIN 10 machine is old and on its last legs. I have both machines side by side so I can still play on the old PC but who knows for how long? I also installed an all-in-1 version that I downloaded in 2021 from Simple. I installed this version in C:\Games\Battlefied 1942. It also runs but has the same problems as the full disk based version which makes me believe it's a graphics problem with both versions. Anyone have suggestions?
Thx.
Ouch...didn't realise it was -11... somehow I didn't check too much
But I'm not actually of the age to play this anymore...should look after my grandchildren ;-)
I suspect that many of us playing this game have grandchildren, including me :-)
I Hope you get unbanned if what you say is true.
Ironfart wrote:Yes Paul it is my internet connection but not my equipment as I have no problems with any other servers than simple.
I believe it is the routing from my ISP.
Moving the server would reroute and probably solve my problem but I wouldnt expect that to happen on my behalf lol.
Ill just have to sit my contract out. ( a year to go) and hope another ISP is better.
Hope my vid entertained you.
IronfartI'm of the opinion that is actually the server. Reason? it happens to different people from different countries at exactly the same time.
I understand if a person randomly lags every now and then it could be his own equipment or ISP, but when you see 5 people all from different countries lagging exactly at the same time what are gonna be the odds? it's gotta be the server. I've seen this literally at least 100 times the past 1-2 years. Basically everyone yells "lagggggg" and if you press tab look at how many players' ping get spiked. Its also usually followed by some poor bastard getting auto-kicked for high ping.
I agree with Ironfart on this because he and I both did multiple tracert tests on the server and arrived at the same conclusion that the problem is in how the traffic is routed. When I use my normal ISP the "lag" is terrible. If I use my cell phone as a hotspot the lag goes away. If I run a tracert on the cell phone hotspot to Simple, the route is different and doesn't hit the hop that we both see timing out. It's the routing to the Simple server that causes the problems. Not all players even in the same country will have the issue but others have a severe problem.
We aren't saying there was no DDOS attack, just that the attack was on top of the "lag" that's been terrible for at least 15 months now.
When I enter an admin command on Tanks a Lot it does nothing. No error message but no effect on the server. Is this because I am using a different PC (laptop) after changing location, PC and ISP? I follow the scores and ranks on Gametracker.com and my total is not being updated there either, not that it's under anyone's control at Simple, but it began failing there at the same time as the failing cmds on Tanks a Lot.
I will return to using my normal location and PC in January so maybe it will all be corrected then. Is there anything I can do now so things work 2000 miles from home?
Next time remind him that chat spamming is against the rules too
I have been able to play by using a vpn or by using a hotspot with my cell phone but neither is very good. Just no freezing with those like a normal connection. Now I have relocated temporarily to USA west coast where my ping is terrible but somehow the lag is not affecting me here. Other than the worsened ping. It does appear to be in the routing. I sure hope the move back to France comes before I return to Ohio the last week of August.
I live in Ohio but visited Mass quite a few times. I like to visit preserved battleships in particular so I try to find the time when I have the chance.
Nice. I've visited there 4 times. I do find Battleships fascinating. Better pictures than I have, though.
Here are 2 traceroute listings. The first is from my hard wired 400Mg connection, max 100 hops. The second is using my cell phone as a hot spot. It still shows the timeouts but it gets there with fewer hops. Maybe that's why I never get disconnected and almost never freeze with it though it's still jerky.
C:\Users\Owner>tracert -h 100 bf1942.team-simple.org
Tracing route to bf1942.team-simple.org [194.88.105.25]
over a maximum of 100 hops:
1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 14 ms 14 ms 14 ms cm-134-228-52-2.buckeyecom.net [134.228.52.2]
3 12 ms 14 ms 42 ms cm-24-53-168-97.buckeyecom.net [24.53.168.97]
4 * * * Request timed out.
5 13 ms 13 ms 24 ms cm-24-53-169-53.maxxsouthbb.net [24.53.169.53]
6 45 ms 47 ms 45 ms te0-15-0-1-5.ccr41.ord03.atlas.cogentco.com [38.104.148.33]
7 48 ms 49 ms 50 ms be2766.ccr42.ord01.atlas.cogentco.com [154.54.46.177]
8 57 ms 54 ms 54 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130]
9 65 ms 63 ms 73 ms be2879.ccr22.alb02.atlas.cogentco.com [154.54.29.174]
10 67 ms 69 ms 70 ms be3600.ccr32.bos01.atlas.cogentco.com [154.54.0.222]
11 127 ms 130 ms 131 ms be2101.ccr42.lon13.atlas.cogentco.com [154.54.82.37]
12 136 ms 137 ms 139 ms be3383.rcr21.rtm01.atlas.cogentco.com [154.54.57.254]
13 142 ms 142 ms 141 ms 149.6.110.74
14 137 ms 136 ms 134 ms 109.236.95.225
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
31 * General failure.
Trace complete.
================================Cell Hotspot=================
C:\Users\Owner>tracert bf1942.team-simple.org
Tracing route to bf1942.team-simple.org [194.88.105.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.20.10.1
2 88 ms * 38 ms 107.243.2.138
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 228 ms 188 ms 197 ms 149.6.110.74
15 226 ms 188 ms 197 ms 109.236.95.225
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
By the way, you can extend the number of hops that Tracert will track. Adding (space)-m100 after the tracert command will increase the number of hops to 100, for instance. I haven't tried that with more than 50 hops, however...
To support Ironfart's findings, this is a tracert to Simple I ran in January after a couple of months of bad connection:
Notice the time-out starts with the same address that Iron shows.
Tracing route to bf1942.team-simple.org [194.88.105.25]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 14 ms 15 ms 13 ms cm-134-228-2-2.buckeyecom.net [134.228.2.2]
3 12 ms 23 ms 13 ms 24-53-168-97.buckeyecom.net [24.53.168.97]
4 * * * Request timed out.
5 22 ms 13 ms 14 ms cm-24-53-169-53.maxxsouthbb.net [24.53.169.53]
6 47 ms 46 ms 52 ms v517.core1.den1.he.net [184.105.253.45]
7 52 ms 50 ms 49 ms 100ge14-1.core1.oma1.he.net [184.105.65.162]
8 49 ms 61 ms 47 ms 100ge8-1.core1.chi1.he.net [184.105.213.1]
9 51 ms 48 ms 48 ms 100ge2-2.core2.chi1.he.net [184.104.192.118]
10 63 ms 64 ms 64 ms 100ge16-1.core1.nyc4.he.net [184.105.223.162]
11 155 ms 130 ms 130 ms 100ge7-1.core1.lon2.he.net [72.52.92.165]
12 130 ms 130 ms 131 ms 100ge0-30.core2.lon3.he.net [184.105.64.238]
13 138 ms 157 ms 135 ms 100ge0-33.core2.ams2.he.net [184.104.193.194]
14 136 ms 134 ms 136 ms worldstream.nikhef.nl-ix.net [193.239.116.249]
15 143 ms 136 ms 137 ms 109.236.95.107
16 137 ms 138 ms 138 ms 109.236.95.227
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Not an OS problem. Clearly a server issue. Another case of users who aren't hitting this problem not believing those who DO have the problem.
The actual statement in English is: "we're taking casualties"
I just logged on to Simple Aberdeen only and placed a Wespe on the ridge where Sepp parks his all the time. I have taken screen shots that show a shell landing in the city which is most definitely visible from the ridge firing position. Hitting behind the city from this position is just a matter of aiming higher until the shot passes over and lands beyond the city. Then you lower the gun so your next shot falls in the city street. If you hit someone beyond the city with the first ranging shot, it's just a lucky kill. The goal is to land your next shot or shots in the city street to kill an opposing player who has grayed the city flag, even if you can't see the flag itself. Sepp does not deserve to be banned for taking ranging shots that land beyond his intended target.
He deserves to be unbanned. Kick or ban him for chat spamming if you want, because he surely does that, but pixelling is not involved in what he did. I suppose now I'll be accused of protecting him now but so be it. He didn't commit the crime he has been banned for.
Sepp often parks a wespe on the ridge to the right from the axis base far enough forward where both south and west flags are visible. the city is visible from the same position. The city flag on aberdeen only server has been moved to the middle of the city road. A wespe can be aimed to pass between the houses and kill any inf attempting to take the city. a few hits will also kill a tank. No pixelling required. I've done both myself. I kinda wish the flag was still in the house so I catch inf trying to take the city when I take the north flag on Allies first minutes. A few shots from north will often kill the inf jumping out of a tank and trying to enter the flag house. Just ask Canadian about that :=)