sorry, three questions about MME record

[kerf]

hi, I faced two problems that i cannot solve it.

1: When I want to record the demo with MME( not ingame record but with OBS such tools), I found the output of the screen is dark no matter how brightness i set ingame( say r_gamma, mapoverbrightbit, overbrightbit, intensity, ignorehwgamma etc.) but when I use IDFe engine it looks normal and good. Any idea about how to make the output of record bright by using OBS studio, for other record tools, it is same( darkness). 


2: I tried to use ingame capture say /capture avi 120 asadasdad, to output the video but after 1.99Gb, it will be divided into one piece......and the movement is slowly, am I correct for general situation to record demo? how about other guys?

3: I found I adjusted the cfg from mme folder but some df_chs codes don't work at all.....should I use other engine instead of MME to record the customized camera path?   

Thank you so much, The first two questions mede me confused that I cannot record my demo successfully...

[ent]

Hi.

1. I did not get which way you want to use: the build-in one or with using OBS and which has a problem.

2. Use pipe instead of avi, it will save you a disk space and still will have a good quality: q3mme.proboards.com/thread/488/q3mme-cutter-demos-double-click

3. DF-specific cvars and commands won't work since they are executed on cgame part of defrag mod, not mme mod. If you want to capture with DF-specific cvars and commands then you have to load cgame from defrag mod folder. To do so copy "start q3mme.cmd" and edit the copy with following:
@echo off
start quake3mme -nosplash +set fs_game defrag +set fs_extraGames "mme" +set r_picmip 0
That means the game will start with using defrag mod folder with q3mme engine.

Recording is special and manual in this case. You need to set the following:
- mme_demoFileName test (or any other value) so it will save the output into /defrag/screenshots/test/
- mme_screenShotFormat pipe
- mme_saveWav 2
other mme_* cvars for your needs (like motion blur etc)
and to start capturing you need to set a FPS value for this:
- cl_avidemo 60 where 60 is desired FPS or other value
to stop capturing set it back to 0.
It is easier to bind that cvar to a key like:
/bind F5 "cl_avidemo 60"
/bind F6 "cl_avidemo 0"

Using this way you will be able to capture with DF-specific cvars and commands yet to keep some q3mme-specific features.

[kerf]

Thank you so much, I will check it.

[Biddle]

I got a fourth question... Is this "new" Q3MME version useable with Urban Terror?
This would be amazing!