http://www.3dgamers.com/games/jedioutcast/)


For all your needs. Hope JKii.net grabs them soon.

Found my problem.. which the solution is listed below :D

Enjoy,
Seether

Oh and don't forget to upload the new and shiny assets2.pk3 file.. :fett:


The assets2.pk3 file is located in the /base/ directory of your client. It was created after you patched to 1.03. You will need to upload this definitely for Linux servers. I haven't looked at what the dedicated Win32 servers need, but probably need to do it there as well.

My Win32 server just hangs with this new .exe. Hosed again...

Using new 103 win/linux dedicated and it is still crashing immediately.

New and shiny assets2 file???

It's in the client updated. Hope you have JK2 installed somewhere.

Grrrrrrrrrrr

wow. this update is truely sh1tty. Gives me a seg fault right after it starts loading... fun.

The segment fault is probably because you didn't put the assets2.pk3 file in the \base directory.

I haven't gone home yet to test this out, but it sounds like in order for the Linux version to work a new .pk3 file needs to be added to /base?

Yup - that's right

Thank god i can SSH into my computers at home while at uni ;)
you need to update the windows client (retail) version, then update your server and copy the new .pk3 file over, otherwise you get the afformentioned seg faults

Hrm, unfortunately, exactly what I was afraid of happened.

I added the new .pk3, and installed the new 1.03 binary, and now everytime I start my server it goes through the loading process, then gives some Segmentation fault and the server crashes.

Looks like no more server.

I have the exact same problem. I have an idea that it might be my assets2.pk3 file thats corrupt, because if I remove it the server starts fine. I assume youre using linux. How are you passing the assets2.pk3 file to your dedicated server dir?
Im at work right now, so I wont be able to fiddle for another 8 hours or so.

I was able to figure it out last night (with Matrix's help, as usual =) )

It was the way I copied the .pk3 over to my server box. I was lazy and didn't check whether it was ASCII or binary mode. Turns out it was the wrong mode.

So, after re-copying it over in correct mode, it acknowledged the .pk3 file and started up.

I will freely admit that I've made that mistake more times than you'd think--hence the reason I mentioned it. Sometimes the simplest things will really screw you up. Glad it worked out. ;)

Originally posted by geronimo27
I was able to figure it out last night (with Matrix's help, as usual =) )

It was the way I copied the .pk3 over to my server box. I was lazy and didn't check whether it was ASCII or binary mode. Turns out it was the wrong mode.

So, after re-copying it over in correct mode, it acknowledged the .pk3 file and started up.
would you mind telling us what the proper mode was? :)

Sorry 'bout that :)

Binary would be the proper mode.