Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - JeGX

Pages: 1 ... 3 4 [5] 6 7 ... 29
Just tested one of the PhysX3 demos of the code sample pack (host_api/PhysX3/Fluids/) with the DEV version I'm working on (v0.6.3.18) and now collisions of a fluid with a static mesh work fine. In the following screenshot, two particle emitters are inside a mesh box:

With prev versions, collisions were not handled with GPU fluids and CPU fluids led to a crash...

English forum / Re: GLSLHacker not starting
« on: April 12, 2014, 01:32:28 PM »
Try the latest DEV version available here:

If the bug is still there, move in another place the following plugins in GLSL Hacker folder:
- plugins/plugin_gxl3d_gpu_monitor_gml_x64.dll
- plugins/plugin_gxl3d_opencl_x64.dll

In any case, let me know.

Big Pictures / ASUS GeForce GTX 750 Ti OC Unboxing
« on: April 11, 2014, 02:00:42 PM »
ASUS GeForce GTX 750 Ti OC (GTX750TI-OC-2GD5)

Unboxing possible thanks to the guys at

Big Pictures / ASUS Geforce GTX 780 DirectCU II OC Unboxing
« on: April 11, 2014, 01:07:42 PM »
GeForce GTX 780 DirectCU II OC (GTX780-DC2OC-3GD5)

Unboxing thanks to the guys at

This GTX 780 has been launched few months ago but it still cool to have some big pictures of that card, better later than never!

Thanks for the bug report. I fixed the shader and it will be available in the next update.

Yes, since v0.6.3.9, GLSL Hacker supports MRT.

There should be a demo in the code sample pack /host_api/MultipleRenderTargets/

To create a render target with two color buffers:

Code: [Select]
num_color_targets = 2
rt01 = gh_render_target.create_v2(width, height, num_color_targets)

When you need to bind color buffers as textures, just do:

Code: [Select]
gh_texture.rt_color_bind_v2(rt01, 0, 0) -- Color texture 0 on texture unit 0
gh_texture.rt_color_bind_v2(rt01, 1, 1) -- Color texture 1 on texture unit 1

In the fragment shader, just declare several outputs:
Code: [Select]
out vec4 FragData[2];

Let me know if the code sample pack is not up to date.
Hope that helps.

University of California researchers have created a system that shows how the brain works in real time, allowing users to navigate right inside their own heads and see their neuronal activity firing in three dimensions, showing “real-time source-localised activity from electroencephalographic signals”.

The two consoles' Graphics Processing Units - called Flipper on the GameCube and Hollywood on the Wii - have a lot in common with their modern PC counterparts, but there are just enough differences to make perfect emulation an absolute nightmare. One quirk in particular is the use of integer math within the console GPU pipeline - as opposed to floating point math which is the norm for PC GPUs.

GpuTest / Re: GpuTest 0.7.0
« on: March 13, 2014, 05:46:23 PM »
I wonder, what's the point of GpuTest if it only works with Nouveau drivers, which are slow and don't even give an accurate measure of the power of my GPU? There's probably something I don't understand.

Fortunately, GpuTest works also with NVIDIA and AMD binary drivers (otherwise GpuTest would be useless, open source drivers are not my passion). Most of the time, my linux boxes have proprietary drivers and tests like TessMark or Julia FP64 work only with NV / AMD binary drivers. I always develop with real NV/AMD drivers and I test open source drivers only before release. Maybe your drivers are not properly installed and something is perturbing GpuTest, I don't know. Wait for the next release of NV drivers for Linux (follow geeks3d news ;) ) and do a new test again.

*Warning: Quite off-topic and not really concerning GpuTest*
On the bright side tho, you Sir may have stopped me from buying a new (unnecessary) video card.
I had a lot of faith in you lol and I was surprised when you said it could just be the drivers.
So I finally found the right tutorial and managed to install the correct drivers. And my video card now does what it's born to do :P
I went from 15 fps on Team Fortress 2 to 200 fps :D!

Thanks a lot JeGX!
You're welcome!

GpuTest / Re: GpuTest 0.7.0
« on: March 12, 2014, 05:01:38 PM »
Thanks for the feedback Stebs.

The engine behind GpuTest supports core profile but it's likely a bad setting in GpuTest. I will look at this issue asap.

GpuTest / Re: GpuTest 0.7.0
« on: March 08, 2014, 10:53:21 AM »
But GpuTest is working now, yay!
If I use the (recommended) drivers, nvidia-319, it fails. But as you said,  most of them work well with Nouveau driver. TessMark's, GiMark and PixMark Julia FP64 aren't working, let me know if you want the log file for them.

It's normal, all these benchmark require OpenGL 3.3 or OpenGL 4.0 support and Nouveau driver is limited to OpenGL 2.1 or maybe 3.0 I can't remember.

I'm glad it works, and also saddened to get the results I feared...
I have a GTX 460 768mb, which is not bad I believe, and get 3-4 FPS on the FurMark test, 1024x640 windowed mode. Same with PixMark Volplosion: 3 FPS.

Same reason: Nouveau driver: Nouveau driver is slow and does not show the performance of your GTX 460. When you will manage to install real NV driver, you will see the difference. So don't panic, your GTX 460 is not dead  ;)

GpuTest / Re: GpuTest 0.7.0
« on: March 06, 2014, 02:34:45 PM »
Hi Pasqual,

yes you've posted in the right forum.

Could you copy / paste the content of the log file (_geeks3d_gputest_log.txt) here? Maybe we'll see something interesting. The second thing you can do is to test the previous version of GpuTest:

because I feel a possible bug with the new GPU monitoring plugin I added in GpuTest 0.7.0. By the way, can you delete and and test GpuTest 0.7.0 again?

If I check ''Submit score to GPU database'', a webpage loads and I can read this in red : INVALID validation ID
Also, when I check this box, and only when I do, I get this message in the console:
(process:26770): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
The GLib-CRITICAL message comes from firefox. Try the following command in a terminal:

$ firefox -v

and I'm sure you will have the same message.

I spent way too much time trying to install the latest NVIDIA drivers (I'm starting to miss Windows...) and I thought I had succeeded... maybe it didn't work, maybe that's why the test fails?
Totally agree with you. The installation of NVIDIA driver is easy and works fine in LM13 but is real pain in LM16. Try to use the Driver Manager to change / update the graphics driver. Most of GpuTest demos work fine with the Nouveau driver.

General Discussion / Re: EVGA GeForce GTX 750 Ti FTW hands-on review
« on: March 05, 2014, 01:14:15 PM »
Stefan, have you tried CUDAMiner?

GpuTest / GpuTest 0.7.0
« on: March 04, 2014, 09:51:08 PM »

Pages: 1 ... 3 4 [5] 6 7 ... 29