|
Post by finalspace on May 8, 2013 19:23:17 GMT 1
It seems the capturing with FBO is not that stable yet, because i capture my demos @ 30 fps / TGA with FBO rendering on and blurframes to 0, i get this: root.xenorate.com/final/firstperson.0000000017.pngWith blurframes greater than zero, 15 for example: I get a "nearly" percect capture, but the first frame is always like this: root.xenorate.com/final/firstperson.0000000000.pngI am capturing using this command: @echo off Start quake3mme.exe -nosplash +set fs_game "mme" +set fs_extraGames "defrag" +set r_fbo "1" +set cl_noprint "1" +set cg_draw2d "0" +set mme_renderWidth "1920" +set mme_renderHeight "1080" +set r_fboBlur "1" +set r_fbomultisample "16" +set r_picmip "0" +demolist "demolst_fp.txt" Exit
And of couse my config: pastebin.com/UhaeraYCWhat i am doing wrong? And how can i fix the second issue with the "Awaiting snapshot" watermark thing?? Of course without FBO rendering it works fine, but is so much slower I have a NVIDIA GTX 580M Graphics chip which is definitily capable of FBO handling (See: www.youtube.com/watch?v=eUbwxTE38TY - uses heavy FBO rendering on my graphics card) on a I7 extreme edition machine. If needed i can post more details. I am using the latest q3mme_1.6_beta33 and of course with almost newest nvidia driver 306.97 (x64 - win7). Would be great if you could check/fix that issue. Greetings Finalspace
|
|
|
Post by santile on May 8, 2013 22:17:04 GMT 1
the same thing happens to me. i can't record with depthframes as well. im using a gtx 650 ti
|
|
|
Post by finalspace on May 9, 2013 11:21:49 GMT 1
Really weird, it seems also without FBO has some issues as well, even without depth frames I started a capture this morning and after i checked some results after one hour i got this for some frames: root.xenorate.com/final/firstperson.0000000357.jpgIt seems that also normal offscreen rendering are broken I also tried disable tga compression, has same issue. Oh man, this was such a great tool, why does this happen now I am gonna search an older version. *With another version - Unfortunatly same version, dont have an older one - same issue: root.xenorate.com/final/firstperson.0000000306.pngI also tried auris config (just included in autoexec and removed the q3config before) - same issue: root.xenorate.com/final/firstperson.0000000312.jpgPlease help!
|
|
|
Post by finalspace on May 9, 2013 11:52:34 GMT 1
Tested it without offscreen rendering - the old way. Works fine so far - No artifacts.
|
|
|
Post by finalspace on May 9, 2013 12:43:00 GMT 1
I reinstalled q3mme which fixed the issues, even with FBO capturing and blur frames enabled.
|
|
|
Post by santile on May 9, 2013 12:59:31 GMT 1
Good to know :] It isn't a major problem to me, since I always capture with blurframes but yeah...
|
|
|
Post by auri on May 9, 2013 14:16:36 GMT 1
Thanks for providing the solution. Glad about it, yet unexpected that a "reinstallation" of mme fixed. Isn't that only a folder you put in your q3 folder? Here are many older versions of mme in case you need them for testing: click
|
|
|
Post by santile on Oct 19, 2014 18:58:43 GMT 1
the same thing happens to me. i can't record with depthframes as well. im using a gtx 650 ti BUMP I figured out what's wrong. Turns out q3mme is crap and can't use r_fbo/r_fbo_blur nor r_fbomultisample while rendering depthframes. So turn these off (and use r_ignorehwgamma 1) and voila, magicly you have depthframes again. (took a ******en while) That is if you want to sacrify your mighty blurframes and/or antialiasing... which kinda sucks :/
|
|