Posts by goodone

it says so on author's page, but luckily, i had no troubles installing it. and yes, it works, not just stands there like in a protected mode environment. i had looked for bits it affects, and yep, working all right. ppl can check it too using device manager, under the hidden devices (turn on hidden devices checkbox from the view menu), search for vlatency driver.

i conclude the warning does not stand for xp sp2, just for server 2003 version of windows, and possibly vista. as much as i was able to see from installer, it should work on all versions of windows, but if one has driver certification (which is an option off by default in xp sp2) turned on, it might not install. the former is usually true for vista and most of server 2003 installations, but one can get it work, just as ryzune suggested.

on the other part, systems it is written for are not server alike, and i guess nobody will try to install vista or server 2003 on them, so, there are no big time worries. anyway, as far as i can tell, because it is beta product (not that it has any bugs or so), author may have rewritten installer so it works on all windows versions, but didn't bother to change the warning.

anyway, i urge ppl to install it, if they have kt133/kt133a mainboards. it solved many troubles with that particular chipset, which is one of the fastest for sdram, making it even better. and ofc, cf works with no problems as a result.

i would not be able to play cf on my regular machine if i didn't bother to check it out, so i am glad i had, at the end.

btw, it is windows xp sp2 machine, patched with criticals, with usual security measures (av+as+firewall), many programs, nvidia graphics, sound blaster live!, tv tuner, modem, network card (abit kt7a mainboard - no integrated stuff). i just love the old perfectly working configuration.

well, if u have money op would require for such a modification, i don't think he would mind, giving he has enough time 4 that. it can easily be made a per basis rule, and eventually it could go into effect quite nicely.

rl money will mean a great deal to both op and server needs.

maybe he'll consider it once.

so, a connection problem, just as i thought. well, i hope u get it all worked up and join our large and fun community as soon as possible.

take a look at this too. u r not alone.

Quote

Originally posted by Fox

owhhhhh

it's not that hard. try a bit and u will manage.

37. tell hipogriff to edit his post and add a number to his suggestion.
38. stay all night awake waiting 4 server to get online.

this is a well known problem that affects sol system, especially when new sound and music data appears: lanes, gates and dk sounds and music. older machines r more prone to experience this issue, and there is little one can do, except to stay in sol as little as possible, and to turn off the 3d sound setting.

maybe op will address this issue in 1.8 version by making sound data a bit smaller.

it's a general problem with freelancer, and happens in vanilla version as well, but not so often as in sol. the problem is in sound engine that makes too many sound data bursts on pci bus, thus making many retries for failed transfer to sound card or southbridge, resulting in client breakdown. 3d sound setting usually makes this data bigger, so it's one of suggestions various mod writers offer to their users. it's affecting via based mainboards mostly, but can happen to others too.

ofc, there r some workarounds:
1. setting latency on pci bus to a greater number, in bios: 64, 126 - makes pci transfer window wider so data can arrive w/o interruptions
2. updating bios - usually includes some changes how pci bus corresponds with sound card on older systems
3. installing a latency patch (via kt133/kt133a/kt266/kt266a/kt333/kt400 and some other based system)

i was having the same sound data problem with cf every time i played on one of via based machines, only to test it thoroughly for days and find the solution in the latency patch. now it works with no problems what so ever. system is generally faster too.

if u know ur way with computer and have an older via based mainboard, latency patch will fix ur and everyone else's problem with this matter. if u don't, setting larger latency in bios will help, 64 or 128 is a good start, but u can test other values too.

this information about the latency trouble should be made visible publicly, so op should maybe stick this topic, or copy it somewhere else. i am not familiar that anyone on swat forum knows about this issue, but i consider topic of higher importance, because many older machines (those fl was made 4) experience this problem.

i agree on that one.

maybe we should change colours a bit. all these red thingies makes ppl bored a bit. maybe something blueish?

as far for tests i have been making with fl server on amd dual core, it performs faster, and of course, never gets to 100%.

these tests were not serious, but my config showed me a certain benefit of multiprocessor machine, so, u should consider that one, in any case.

and yes, since microsoft made the game, windows does good job into splitting processes between cores, no problems encountered for days of testing.

for the need of fl server, from best to worse:

1. 175
2. 165
3. 148

m8s already explained why.

ddr2 based memory server is better solution, imao.

this is a sound related problem. fl is known to push too much sound data to the system bus. turning off 3d sound might help, and is suggested if u experience any kind of troubles, but for some older system, with via kt133/133a chipsets for example, u may need latency patch, or at least bios update.

it seems like u r having big time connection problems, at least to cf server.

where r u from? that will give us some real insight, i think.

it aint possible.

Quote

Originally posted by SWAT_OP-R8R
ok - then lets limit the use of missiles a bit
is 10 missiles ok? or do you want me to do it like with the coalition torpedo -> use of cargospace and therefore different amount of missiles depending on the ship

it is a very good idea, op. big ammo, like missiles, torps and maybe mines, should take up the space in cargo. i like this idea very much. u can leave an initial ten slots free that don't take cargo space, and if a player wants more, then... goes the cargo space.

it is not strictly a SMG policy, but i do agree on everything Burro said.

as i said before, we dnt have such a great community and player numbers to insist on a one char per person policy.

it would be a simple suicide for crossfire.

take a look at this.

u should check this also.

it was made 4 me in png, and i am not into coverting it... maybe l8r, but, if it works, i dnt have to.

still didnt install any of photo editing software... and for such a small thing, i wont budge.

it must b something about privys post about multichars. he opened a new topic, instead of a reply to previous one.

tnx m8.

4 future posts, plz state a browser and a version if u dnt mind.