Not dual core compatible afaik... mainly due to dual core not being around when the game was made.


No patch to make it so, come on - this is FL with MS remember

Edited by - Chips on 5/29/2006 4:04:52 PM

Speaking of dual core (apologies for gravedigging here) - I just switched from an Athlon64 3700+ to an Athlon64 X2 4200+ and the game has become quite choppy. Has anyone else noticed performance issues with a dual core CPU + Freelancer?

I put together an Athlon x2 3800 PC- I don't have any problems with FL on it. I do notice a slower than expected login, though.

system specs:
Athlon 64x2 3800+
1GB DDR400 RAM
ASUS K8N-VM-CSM
ATI Radeon X600 All-in-Wonder 256MB
XPPro SP2

Chris Bates

Another issue I heard about is that FLserver apparently is somewhat crash-prone on dual-core or dual-CPU systems due to threading issues. Can anyone confirm this?

I haven't run into any problems running either dual 3.0 processors or the new Intel Core 2 Duo 2.13GHz processor.

The Asylum 51 server has been running dual 3.0 intel processors for a long time and they haven't given Glock any problems that I'm aware of.

yes we at monkey universe have been running a dual core since feb 2006, running on both cores has caused problems you need to set the affinity to run on only one core. if you use ioncross as long as ioncross is set to one core it will only reboot your server on on the same core ioncross is running on.

Triple

but then again I believe we started running FLshell around the same time so who knows maybe its the cause.

Triple

Running flshell could be the problem but I don't know. It's possible but since I was on vacation when the flshell news was posted and it is not hosted here on Lancers Reactor, why it's not hosted here I couldn't tell you. I didn't bother finding out about how it works.
Maybe Chips knows something about flshell he was the one that posted the news about it.
Good luck finding any information on the flshell website because it seems to be offline... at least it was when I checked http://www.skif.be/
The fourms seem to be offline also http://www.skif.be/forum/viewforum.php?f=1

The only thing I found on flshell was the news post here on Lancers Reactor http://www.lancersreactor.com/t/news/newsitem.asp?id=3479&category=Freelancer and the news post does not mention dual processors or dual core processors.

And you're talking about running a server probably with IONCROSS too which is different than just running Freelancer on your computer. Unless of coarse you're playing Multiplayer, in that case you have to start flserver.exe first in order to connect to your own server in Multiplayer mode.

Hm. Well, in my case I'm running Ioncross + FLshell + FLserver.

According to the Cheaters Death people (which is where I realized I found out about this dual core issue) FLserver and Ioncross can crash sometimes due to the "dual CPU" situation.

I'd rather not have to run Ioncross *and* FLserver on the same core, as that kind of defeats the purpose of a dual core system. However we are experencing a few unexplained crashes in the Phoenix RPG and I'd like to make sure I didn't waste my money on a P4 D 805.

Sorry for gravedigging. I just wanted to let people know that there is a known issue with Windows and dual core processors, and Microsoft has a hotfix for this.

http://support.microsoft.com/kb/896256

Any New News on this?

Ive got a problem myself.

Freelancer was running fine on my computer until i added another gig of ram (so now ive got 1.5 total, one 1 gig card and one 1/2 gig card). My problem is that whenever i try to go into single player, the game crashes immediately. No error messages, no nothing. The game just stops and i get thrown back to my desktop. But what is wierd is that i can still play multiplayer without any problems at all! Anybody got any ideas as to why this is? Ive tried everything on the microsoft help site, but i just get the same results.

I'm guessing there is a corrupted save file and you may have to delete all saves
that usually works when people have the start crash you mentioned

You also might just have a bad RAM module.

Try http://www.memtest.org/