bump for interest

Hi /b/rother

Privet

Wasnt talking to you /f/aggot

now there's no reason to not make get quaked 4...

...i think i'll leave it now

So then transfer the pak0 from QL to your q3mme folder? lol

Now I have this only , but this is not enough:
1. Download QL mappack for quake3 - http://rutracker.org/forum/viewtopic.php?t=4521822 and put on baseq3 folder in quake 3 directory
2. Export the ql-demo in xml file via qldt (quake live demo tools)
3. Open xml file via notepad and change parameters: 73 to 68 and config index 529+x to 544+x for players in demo settings - http://s1.ipicture.ru/uploads/20140421/d2i4vx4R.jpg , it allows to display in q3mme the all players and save
4.Import the modifed xml in qldt and save demo via point "editing", qldt make it automaticly 68 protocol for q3mme
4.in q3mme console apply the " /s_initsound 0" for prevent the fall in desktop, because the sound does not work properly in incomplete conversion

This is uncomplete conversion, glithces rewards,fragmessage absent sound and confused items

If two players in demo that little glitches, but more players a have this - http://www.youtube.com/watch?v=iuPNRrJ4XoA rail glitches

Waiting for your thoughts and suggestions for helping to make the complete conversion dm_73 to dm_68 protocol

Why do you want to use q3mme over WC? I've heard great things about q3mme camming, but other than that I believe they're quite similar. Perhaps try asking dKsL, perhaps he knows...

I know several people who have created ql movies on in the q3mme.

Are you sure? I don't :p

q3mme is better than wolfcamql in such areas: blur and free camera control, lighting for textures colder, it's easier to look

wolfcamql (bloom off) - http://s1.ipicture.ru/uploads/20140421/G83T1sTy.jpg
q3mme - http://s1.ipicture.ru/uploads/20140421/G7424WTm.jpg

In wolfcamql I tried to do the same cold light of texture than q3mme, but I could not get same effect

the wolfcam one looks much better

lol no

looool, no

I had to try the same wolfcam screenshot myself, because I'm convinced yours looks shit.

EDIT: do you have DoF on in in WC? That might account for the blur...

Here's mine, but I still agree that q3mme's looks nicer.

Also what do you mean by cold texture?

How you make it http://i55.servimg.com/u/f55/16/10/00/84/shot0028.jpg in wolfcam??? its good, but q3mme picture - http://s1.ipicture.ru/uploads/20140421/G7424WTm.jpg is better imo, your picture in the middle

I try different combination of this settings, but not gife result

seta r_lightmap "0"
seta r_vertexlight "0"
seta r_intensity "1"
seta r_enablePostProcess "1"
seta r_lodscale "50"
seta r_dynamiclight "0"
seta r_ignorehwgamma "1"
seta r_enableBloom "0"
seta r_enableColorCorrect "1"
seta r_texturemode "gl_linear_mipmap_linear"
seta r_contrast "1"

Dof work only mme_savedepth video or both?

Most of my settings are default, so I'd suggest you've messed something up somewhere.

seta r_lightmap "0"
seta r_vertexlight "0"
seta r_intensity "1.3"
seta r_enablePostProcess "1"
seta r_lodscale "5" //I don't see any change altering this cvar. Apparantly "Level of Detail scale adjustment". Do you know about it?
seta r_dynamiclight "1"
seta r_ignorehwgamma "1"
seta r_enableBloom "0" <- can use 1, some bloom can be nice
seta r_enableColorCorrect "1"
seta r_texturemode "gl_linear_mipmap_linear"
seta r_contrast "1" <- can increase this slightly
seta r_mapOverBrightBitsCap "255"
seta r_mapOverBrightBitsValue "0.7" <-this is quite important, otherwise I find the map has really bright parts
seta r_mapOverBrightBits "2"

I don't know about depth of field, but there is:

seta mme_saveDepth "0"
seta mme_depthFocus "0"
seta mme_depthRange "200"

but I've never tested them apart from once a while ago with WW. Thought it was unnecessary, but it can look cool. Don't remember if it works for screenshots :/

try
r_mapOverbrightBits 1
r_mapOverBrightBitsValue 1

My QL looks just like your q3mme screenshot. and in QL I use:

seta r_ignorehwgamma "0"
seta r_overBrightBits "0"
seta r_mapOverBrightBits "2"
seta r_intensity "1.3"
seta r_contrast "1.0"
seta r_gamma "1.0"

You're right about wolfcam it's too shiny, r_mapOverbrightBits 1 made it really very similar to QL for me.


My r_mapOverbrightBitsCap is 255 in both QL and wolfcam, but you may want to fiddle with that too.

wolfcamql
my defaults: http://i.imgur.com/eMSRbFQ.jpg
with r_mapoverbrightbits 0 for less map brightness: http://i.imgur.com/Ajh7xc2.jpg
r_ambientscale 0 for darker player models
and btw:
r_ext_multisample 4 or nvidia fxaa
r_ext_texture_filter_anisotropic 1
r_ext_max_anisotropy 16

r_mapoverbrightbits 0

I tried that when I was testing, it just made all the map geometry black for me, lol.

I try this later

I make this in wolfcam! - http://s1.ipicture.ru/uploads/20140422/vUJ5PdHF.jpg
seta r_overBrightBits "0"
seta r_overBrightBitsValue "1"
seta r_mapOverBrightBits "2"
seta r_mapOverBrightBitsValue "1"

Yakumos right

but question about converting ql demos to q3 into force

iirc qldt converted the demo format?
On mobile atm or i'd check.

You'd almost certainly have to xor the pk3s with the maps and textures too so they're just Q3 format (zip files) again, as I assume q3mme hasn't been updated with any ql specific code?