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 ... 786
91
Support / Re: Only thing rendered is the SkyBox
« on: June 19, 2017, 10:55:58 pm »
Have you tried to remove the skybox render call? It doesn't do anything useful at this stage, because you'll blit over it anyway...!?

92
Support / Re: Only thing rendered is the SkyBox
« on: June 19, 2017, 01:02:09 pm »
That doesn't really help. I need the complete render sequence for all buffers and the final render to the screen.

93
Support / Re: Only thing rendered is the SkyBox
« on: June 19, 2017, 10:59:11 am »
Ok...and that happens in which case exactly? A code snippet would be helpful.

94
Support / Re: Hardware renderer frame
« on: June 19, 2017, 07:59:08 am »
Have a look here: http://legacy.lwjgl.org/javadoc/org/lwjgl/opengl/Display.html

That's what the hardware renderer uses. The methods in it are all static, so you don't need an instance of it.

95
You can't use the an input buffer as an output buffer at the same time.

96
Support / Re: Only thing rendered is the SkyBox
« on: June 19, 2017, 07:56:15 am »
No idea. Do you have a stack trace?

97
Support / Re: Only thing rendered is the SkyBox
« on: June 18, 2017, 02:45:25 pm »
No, you need all of them. If you omit one of them, the corresponding buffer (screen or texture) will never be swaped.

98
Support / Re: Only thing rendered is the SkyBox
« on: June 17, 2017, 09:51:39 pm »
It won't crash without the dummy world, it just might blit wrongly. It will crash without the display calls, because that will cause an OOM after some time. The display call displays the results in the render targets, not on screen.

99
Support / Re: Car Reflections
« on: June 16, 2017, 05:18:49 pm »
It might be that the shaders don't support transparency as they are, but that can be added easily. However, before dealing with that, I would like to know what exactly are your desired results and what you get instead. A screen shot might help...

100
Support / Re: Only thing rendered is the SkyBox
« on: June 16, 2017, 02:17:56 pm »
The dummy world is a hack for setting up the blitting context properly, when the actual frame buffer isn't used for any other output then 2d blitting. It might not be needed in current versions, so you can try to leave it out and see if that works too.

What the code does is: Render the left eye's view into a texture, render the right eye's view into another texture, blit the resulting textures into the actual frame buffer. That's the easiest way, because otherwise, you would have to render both views into the frame buffer and that's not really possible without a lot of hassle...if even...

101
Support / Re: Camera rotation
« on: June 15, 2017, 01:17:43 pm »
There's calcAngle() in SimpleVector. You could use it to calculate the angle between, for example (1,0,0) and the vector returned by Camera.getXAxis(), but I'm not sure if this the best idea. Another way is described here: http://www.jpct.net/forum2/index.php/topic,2254.0/

Anyway, I'm still confused about what you actually need. Or in other words: I don't see the difference between the video example that you've posted and what the HelloWorld example does!? I'm not sure what exactly you mean by this single touch/multi touch thing...!?

102
Support / Re: Only thing rendered is the SkyBox
« on: June 14, 2017, 09:02:08 pm »
Must be some driver issue then...no idea what's going on. Anyway...

For VR, there's this: http://www.jpct.net/wiki/index.php?title=Example_for_Google_Cardboard or maybe this: http://www.jpct.net/forum2/index.php/topic,4814.msg32913.html#msg32913. You can't use two FrameBuffer instances at a time, because they are bound to the context and there can be only one. But you can use multiple render targets, which is basically the same thing. See the second link for a simple example that doesn't use any VR API, just pure jPCT-AE.

103
Support / Re: is result of setboundingbox permanent?
« on: June 14, 2017, 08:57:13 pm »
The optimization applies to quads as well. It's still in there, just not used anymore in all cases. I don't think it will impact performance in any way noticable.

104
Support / Re: how to identify the version of the engine jar file
« on: June 14, 2017, 08:56:16 pm »
Config has a getVersion() method. The jar itself doesn't contain the version number.

105
Support / Re: is result of setboundingbox permanent?
« on: June 13, 2017, 09:29:03 pm »
Now that was a funny one...For single polygon objects, the engine applied an optimization for the bounding box culling, so that it actually used the polygon for culling, not the box (less work to do that way). That has been added to speed up particle effects on slower devices, but it obviously couldn't handle your special case. This version should fix the problem: http://jpct.de/download/beta/jpct_ae.jar

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