pk3 upstream problem for wolf et on server

(FireballLightning) #1

Hi.

I am having a problem that I was wondering if someone could help with. I have a wolf et LAN server, which will upload campaign and other pk3 files like whaleclient and such, but it will simply not upload soundpacks (did not try skin packs).

I have checked my server.cfg, I have…

set sv_pure “1”
set sv_allowDownload “1”

And the soundpacks tested do work when I manually copy the pk3 from 1 installation to the other and then connect, I have 2 installations on 1 pc.

i also have my client set to receive all 3 types of downloads in options. for the soundpacks named something like “pak5.pk3” (matts band of brothers v2 pack), i previously tried to rename it if i would not get an “official missing pak error”, before trying the manual copy method.

Anything I’m doing wrong?

thx for help in advance.

(FireballLightning) #2

i know about 6 hours is kind of fast to bump on my own request, but i haven’t got anything better to do at the moment, and i thought i’d get a swarm of responses on these official developer forums, maybe i was expecting something a bit unhuman.

if anyone has any idea why sound-only packs won’t upload from my server, will they come forward plz?

here’s some additional info;
server’s on etmain, but it’s modded clientside with whaleclient which does upload and have it’s own sounds, pc’s on windows vista ult x64, running only windows firewall for blocking traffic.

just proving i’m not a one-time poster. and anyone think this might be better posted in modding section on these forums? just a thought.
thx.

(Sauron|EFG) #3

I don’t know what’s causing the problem, but I must say that naming soundpacks like the stock pk3 files (“pak5.pk3”) sounds like a really bad idea. :slight_smile:

Does the whale client overwrite the cgame dll in etmain (sounds like another bad idea), or how do you manage to keep the server=etmain/client=whaleclient?

Have you tried it with a real etmain (no whale client), or with etpub + whaleclient?

(jaybird) #4

You need to set up an external redirect. The legacy download system goes very slow due to engine limitations.

(mortis) #5

Read my Redirect Server tutorial and see if that helps…

(FireballLightning) #6

thx for the inputs.

pak5.pk3 actually, is what “matts band of brothers version 2” soundpack was called, inside the full .zip file i had to extract initially

it was in my opinion, poorly named in imitation official paks 0, 1, and 2. so when i didn’t yet change the name, and tried to upstream it from lan to my client, it gave me a missing official pak error, even if i click reconnect.

i probably made it more confusing even mentioning this soundpack lol, i know others aren’t working either tho, i like to grab them off of filefront

no i havent tried etpub on my server yet, or any serversided mods, but i have tried without whaleclient since it does have its own sound folder…still no luck…the sound-only, or mostly sound-based pk3’s are the only ones not upstreaming, very weird.

i would have set an ext redirect, but my problem seems to be that its not going slow, its totally skipping that files upload and letting the client join without a forced download, despite sv_pure, and to my tests this also proved that i could be listening to the pack while others arent, i want all clients to hear it

this couldnt happen to be some kind of formed bug in et, would it?

if any of you here have ideas, i can should be able to follow the instructions, or most, hopeful this can be resolved.

(SCDS_reyalP) #7

You should never use files named pakN.pk3 unless you are making a total conversion mod.

Putting paks in the fs_game directory, rather than etmain, usually forces them to be downloaded.

(FireballLightning) #8

ok, after quite some time trying making attempts at this, from making an immitation of a modfolder by simply making a folder in the et directory and making the lan reference to that, all the way to even downloading a serverside mod for et then using fs_game in the startup script on that too, i found out my problem was probably either or both installing wolf.exe into a different directory to make my second installation rather than click/drag/copy, and possibly the way i had that startup script, not having fs_game and other stuff maybe.

both the custom folder i made and the mod folders make it work now, thx.