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 - Mr_Chaos

Pages: [1] 2 3 4
1
Bugs / Re: AWTCanvas not updating when SwingThread is under heavy load.
« on: August 09, 2017, 07:14:41 pm »
That's strange, because they should be in the same thread. Have you checked if they actually are? It is possible to work with different EDT's for different components (albeit that's a pain in the a... but some people won't listen...).

Or...maybe the table is sorted in the EDT, i.e. actually blocking it while doing the repaints by itself?

It's very strange, because all other swing components also still update (we have a JTextField with the current time, and it updates fine).

Any idea how I could debug it ?

2
Bugs / Re: AWTCanvas not updating when SwingThread is under heavy load.
« on: August 08, 2017, 10:15:10 pm »
Not really. How exactly do you define "heavy load" for the EDT?

That's a good question, we have a table (Jide) which is updated many times each second, and if we sort the table, suddenly the awtcanvas stops updating, but the Swing table still updates

3
Bugs / AWTCanvas not updating when SwingThread is under heavy load.
« on: August 07, 2017, 08:18:56 pm »
I have a strange problem, normally my program runs fine, but when the EDT thread in under heavy load the AWTCanvas freezes.

The SwingUI is updated, but the AWTCanvas is not.

Has anyone seen anything like this before ?

Code: [Select]
    buffer.clear(frameBufferBGColor);
    world.renderScene(buffer);
    world.draw(buffer);
   
    buffer.update();
       
    buffer.displayGLOnly();
   
   _canvas.repaint();


4
Support / Re: Limit of moving object3D
« on: February 15, 2015, 05:18:08 pm »
Then I think that's the solution

5
Support / Re: Limit of moving object3D
« on: February 14, 2015, 07:02:05 pm »
I could half it, by having some Object3d which will be empty carts and some Object3Ds with bags, that way I only have 25000 objects.

Could draw distance help here, so some of the objects won't be drawn each frame ?

6
Support / Re: Limit of moving object3D
« on: February 13, 2015, 09:19:39 pm »
I have to show 25000 carts each consisting of the cart (1 object3D) and 1 item in the cars (another Object3D).

But i'm thinking if maybee I can change the view distance, so not all of the objects are visible at a time.

7
Support / Re: Limit of moving object3D
« on: February 13, 2015, 07:08:01 pm »
:/

Could you make one large Object3D and move it's vertices manually that should make 1 drawcall, right ?

8
Support / Limit of moving object3D
« on: February 13, 2015, 12:43:05 pm »
I was wondering if there is a limit to how many Object3D you can have, I'm looking into a requirement that might mean we have to have 50000 objects on screen at the same time, running at 30fps.

9
Support / Required OpenGL version
« on: February 12, 2015, 01:48:02 pm »
Someone want to run a program using OpenGL om a WMWare view client.

So they want to know which version of OpenGL is required to run JPCT ?

10
Support / Re: Replacing a texture leads to (Native memory leak)
« on: February 09, 2015, 07:49:55 pm »
It works now, handle count is completely stable and the same is my Memory usage

11
Support / Re: Replacing a texture leads to (Native memory leak)
« on: February 09, 2015, 01:41:08 pm »
They are lost forever, never reclaimed.

When my program reached about 2500 handles it's using > 5GB native memory

12
Support / Re: Replacing a texture leads to (Native memory leak)
« on: February 09, 2015, 09:55:37 am »
Ok, by changing it to use the IPaintListener the logs look a lot better, the problem is that I still have a handle leak.

I am using a BufferedImage to create the texture from, don't know if that might be a problem ?

Code: [Select]
********************updateElementsTexture********************
oldTexture=<com.threed.jpct.Texture@24fa5c93>
Texture 2 added for unloading (1)!
Loading Texture...from Image
newTexture=<com.threed.jpct.Texture@324895c0>
********************updateElementsTexture********************
Textures to unload: 1
Unloading texture 2
texture 2 unloaded from GPU memory!
New texture's id is: 2
New texture uploaded: com.threed.jpct.Texture@324895c0 in thread Thread[AWT-EventQueue-0,6,main]

13
Support / Re: Replacing a texture leads to (Native memory leak)
« on: February 08, 2015, 09:50:27 pm »
Ok, the logs helped a bit, but I cannot figure out what is wrong.

It seems that whenever i replace the texture the old texture is uploaded as well as the new one.

So the leak is that both the old and the new texture exists ... or something.

Using the taskmanager I can see the handle count increate whenever i replace the texture

Code: [Select]
Texture 2 added for unloading (1)!
Loading Texture...from Image
Textures to unload: 1
Unloading texture 2
texture 2 unloaded from GPU memory!
Allocating 4194304 bytes of direct memory for texture: com.threed.jpct.Texture@76ce21e7
Creating new disposable buffer of size 4194304
Caching 4194304 bytes of direct memory!
New texture's id is: 2
New texture uploaded: com.threed.jpct.Texture@76ce21e7 in thread Thread[AWT-EventQueue-0,6,main]
New texture's id is: 6
New texture uploaded: com.threed.jpct.Texture@51a3adb in thread Thread[AWT-EventQueue-0,6,main]
updateElementsTexture
Texture 6 added for unloading (1)!
Loading Texture...from Image
Textures to unload: 1
Unloading texture 6
texture 6 unloaded from GPU memory!
New texture's id is: 6
New texture uploaded: com.threed.jpct.Texture@51a3adb in thread Thread[AWT-EventQueue-0,6,main]
New texture's id is: 7
New texture uploaded: com.threed.jpct.Texture@66c9cfd2 in thread Thread[AWT-EventQueue-0,6,main]

14
Support / Re: Replacing a texture leads to (Native memory leak)
« on: February 08, 2015, 06:40:35 pm »
BTW: Log level should  be debug, not just verbose.

Tried with both, wasn't sure which was most important

15
Support / Re: Replacing a texture leads to (Native memory leak)
« on: February 08, 2015, 05:56:47 pm »
Forgot

Code: [Select]
Logger.setLogLevel(Logger.LL_VERBOSE);

But still this is what I get

Code: [Select]
updateElementsTexture
Loading Texture...from Image
Allocating 4194304 bytes of direct memory for texture: com.threed.jpct.Texture@32cb56e6
Caching 4194304 bytes of direct memory!

Pages: [1] 2 3 4