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

Pages: 1 ... 5 6 [7] 8 9 ... 795
91
News / Forum upgraded to 2.0.15
« on: January 16, 2018, 05:29:27 pm »
No text!

92
Support / Re: Memory consumption with Config.maxPolysVisible
« on: January 16, 2018, 05:28:53 pm »
No, but that list actually isn't that expensive. I'm really wondering where all your memory is gone!? Are you using very large textures or something like that.

93
Support / Re: Memory consumption with Config.maxPolysVisible
« on: January 16, 2018, 08:02:19 am »
Then just increase the heap memory, or isn't that an option? Or consider to use compiled objects http://www.jpct.net/wiki/index.php?title=Compiled_objects, which will use much less space in that particular list.

94
Support / Re: Does TextureManager Operate on a Parallel Thread?
« on: January 13, 2018, 12:09:38 am »
It actually can't fail. It's a simple list of names associated with texture instances. addTexture is an extremely simple operation. If you can't assign a texture, chances are that it hasn't been added by your code. You can obtain all the names from the manager. Try to check if it contains the ones that you think it should.

95
Support / Re: Does TextureManager Operate on a Parallel Thread?
« on: January 12, 2018, 05:51:41 pm »
No, it doesn't. There are no threads on jPCT other than the ones used by the software renderer (optional) and the SEAT Renderer. If you add a texture, it's in there when the method returns.

96
Support / Re: rotateMesh Bug
« on: January 11, 2018, 09:58:02 pm »
Well...I can't. strip() strips away stuff that is needed to do it, so...

97
Support / Re: rotateMesh Bug
« on: January 11, 2018, 08:28:22 am »
No, just some memory.

98
Support / Re: rotateMesh Bug
« on: January 10, 2018, 06:05:26 pm »
Just don't call strip() on the object and it should work.

99
Support / Re: rotateMesh Bug
« on: January 10, 2018, 03:36:34 pm »
Most likely because you've stripped the object it's being called on.

100
Bugs / Re: Points are always microscopic in OpenGL 2
« on: January 08, 2018, 08:25:13 pm »
No, that's actually not surprinsing. ES 2.0 cares about lines width, it just has not method to set the point size, because of...reasons. For me, the new jar actually works fine simply be using the method to set the line width and apply it to points. It might be that some driver do this and some don't. Which device are you using? Can you try it on another one with a different GPU?

101
Support / Re: Use 'setExternalID' to show videofile on polygon?
« on: January 08, 2018, 05:20:10 pm »
Not sure...first  of all, the warning output of the driver and such doesn't mean anything. It's a warning so that it shows even if people configure the Logger class to be almost silent.

I've send a PM to raft, who did render some video onto a polygon. Maybe he can help. At first glance, your first approach looked fine to me but then again, I never really did this myself.

102
Bugs / Re: Points are always microscopic in OpenGL 2
« on: January 08, 2018, 05:14:07 pm »

103
Support / Re: Use 'setExternalID' to show videofile on polygon?
« on: January 08, 2018, 10:15:09 am »
Can you verify that the texture actually has the external ID properly set and that it is a valid ID!?

Are you getting any log output of what's going on? You might as well set Config.glDebugLevel to 1 and post the (important) output here.

104
Bugs / Re: Points are always microscopic in OpenGL 2
« on: January 08, 2018, 09:13:35 am »
That's not a bug. OpenGL ES 2.0 doesn't support point sizes directly so I left out the option to set the width back then and never revisited it. I'll look at it again...


105
Support / Re: Calculate visibility of an Object3D
« on: December 29, 2017, 11:27:40 pm »
Wouldn't two fovs in one image look strange anyway?

Pages: 1 ... 5 6 [7] 8 9 ... 795