VOGONS

Search

Common searches

Search results

Display options

Display options

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-27, 16:53

I will look into it later. It sounds interesting 😀 And even 32bit color. wow. But it is sure still 16bit quality there, isnt it? Or are it real 32 bit? Was the sky really because of the color depth and fog? I thought it was one of the graphical advantages Glide had back then over D3D.

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-27, 10:17

NFS 3 offers worse resolutions and like NFS 2 worse graphic! Especially the skies look much worse on Direct3D. But if Glide really has no Texel 3 problem anymore I definitely have to try again. Since NFS Porsche doesnt look worse with D3D maybe it would be nice to be fixed too - or I just use Voodoo …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-27, 01:55

dgVoodoo 2.51, Glide 3x Napalm, 32bpp. 16bpp works nice in this case I'll try out the Glide of dgvoodoo 2 on NFS 4 later. Maybe all the other Glide Wrapper (nGlide and Zeckensack I tried previously for NFS 4) just were worse than dgvoodoo. May be. Most interesting would be NFS Porsche though. There …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-25, 21:11

Texel setting is from 0 to 7 if I remember correct. While Texel of 3 is center and 0 is top left. And NFS needs it top left. And it is the case for more than the NFS games: http://www.tomshardware.co.uk/forum/133383-33-texel-alignment or here it is mentioned too: http://forums.anandtech.com/ …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-25, 19:53

Can you show a screenshot how "bad" fonts look in the NFS3 I would have to install it again and so on. But its similar to the NFS 2 screenshot of lap record time on left bottom. It looks pixelated and bad. NFS Porsche is even worse. and how it have to look How? This would require me to run it on a …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-25, 18:56

what bad idea you speak of? Its really a frustration to see NFS still in bad fonts, NFS porsche sure still no shattered windows if car upside down and still evil ugly fonts as well and still eventually even have the headlight problem, just because no option to change texel even if dege would be able …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-25, 18:49

It fixes all the games which use other Texel value than 3. And you wont offer it, because computer noobs dont understand it? Seriously? That would be a great disappointment o.o And the already existent options understands my grandma? Thats the worst reason I ever heard. Then make a expert mode, …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-25, 17:43

We were talking about that previously but I don't want such a setting. It would just confuse the average user. Then they should read how to use their software. Seriously - settable Texel would finally fix NFS 3, NFS 4, NFS Porsche for having ugly font and that headlight problem. It must be zero for …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-21, 12:17

Another question: You said in readme you could fix the z-fighting light problem on nightraces for NFS 3/NFS 4 by using a 16 bit Depth Buffer. Now I'm confused. Because: Do you remember the Texel Alignment Setting on old graphic cards? Default is 3. But NFS 3, NFS 4 and NFS Porsche need it to be set …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-18, 15:40

Try disabling antialiasing (MSAA). No option for me. The game needs AA badly. I'm also very sure that the MSAA code of dgvoodoo wasnt changed compared to 2.50. In 2.50 it works fine. _____________ On the other hand on 2.50 Need For Speed 2 refused to run in forced 2560x1600 or any other resolution. …

Re: dgVoodoo 2 for DirectX 11

Posted on 2016-03-18, 01:55

I've got a problem with 2.51 with Blood 2. My windows mouse pointer is flickering into the game for some ms frequently. It didnt happen with v2.50. Maybe it has something to do with the new "capture mouse" option? It doesnt make a difference if checkmarked or not. The problem is only solvable by …

Re: DOSBox tearing & renderer idle

Posted on 2015-01-12, 22:29

was still teared. maybe it needed vsync enabled? but one thing is interesting now: svga_s3 is without tearing even without that .com file. But it is 20fps slower :( edit: With vsync enabled it isnt tearing with vesa_nolfb and .com file now. But the fps is even lower here. Just 30fps. Thats way too …

Re: DOSBox tearing & renderer idle

Posted on 2015-01-12, 17:20

BTW, the aspect ratio of Blood is wrong. I know. It should be 4:3. But the stretching doesnt disturb me that much on my 16:10 monitor. _ a .com file? Do I run it into dosbox? But if so which vga device of dosbox before the com file? vesa_nolfb?

Re: DOSBox tearing & renderer idle

Posted on 2015-01-12, 16:49

But this way the video encoder gets frames by the graphic card. Otherwise it wouldnt everytime when the renderer idles. And this already happens when you stop moving the mouse on a static background or loading screens etc. Not very nice if you want to capture video. But I see what you mean. So the …

Re: DOSBox tearing & renderer idle

Posted on 2015-01-12, 16:17

awww *-* just add it above SCALING That did it :) I just wonder: Why it isnt the default behaviour of the box? Has the render idle any sense? :( honestly: The whole perfomance got a huge buff now. Instead of 50 to 70 fps swapping in blood while recording I have now a flat 70fps. Its so butter smooth …

Re: DOSBox tearing & renderer idle

Posted on 2015-01-12, 15:39

You can stop "render idling" if you modify a shader (point.fx for instance) and add "bool forceupdate : FORCEUPDATE = true;" somewhere at the top. Use output=Direct3D,pixelshader=point.fx,scaler=hardware2x. Didnt work for me :( Does the line have to be at a specific place in the point.fx file? Also …

Page 3 of 4

Go to top of page Go to top of page
Close window
Close window