[GU]elmur_fud;2609942 said:I find it illogical to think that every custom player model, map, mutator, etc. will get pushed into one massive pak file.
I think you've missed the point completely. Each map and it's associated assets would be one pak file. It makes perfect sense, since what's easier to install than just dropping a single file into a directory?
It's too early to say yet. It will probably just be a big pak file you drop where ever, though code based mods is a complete unknown.
[GU]elmur_fud;2609903 said:...
So yes I can go look in the folders and see Content/Paks/bigfatpakfile.pak. But there is no way that all content would be bundled into a single pak file and almost as unlikely that it would be multiple pak files in the same root directory when launched. ...
You didn't have to do that with UT3. You also wouldn't have to do it in the new UT either. You can put the files anywhere inside the content directory.
It really shouldn't matter. Hopefully the new UT will have a content manager and even if you download something outside of the marketplace, it will be like a "umod" or something and put the files where they need to go.[GU]elmur_fud;2610015 said:I know there were work arounds but that is the default. Clearly I didn't like it and so I fixed mine. (I personally just cut and pasted all of mine into UT3's root directory). The system confused a lot of people though if the complaints on the UT3 forums were any indication.
It does occur to me now though, that with the content market place it may push the files to the appropriate location eliminating the need for installing it manually.
... Technically, it is wrong to install user files to the Program Files directory. Simple solution: don't install there by default.
Package locations are irrelevant. You can reference any asset you want.
More likely to be a difference between the collision flags in either projectile. Would be an easy fix.
https://mega.co.nz/#!XVwU3LjD!Z5BZJ19FD3t0oe6TVLQSzFzxZz8qhUe8nloDdjdfbz0
Looked up making a 32bit. Unreal Engine 4 simply doesn't support it.
We put a new build up on 9/12/2014 - now including Win32 client.