Video

Hungarians say "ehh" instead of "uhm"

It's not "Ehh" it is ööö

haha igen@@PeterIsza

@@PeterIsza sorry, i don't speak alien language

@@pixelsymbols learn Hungarian in 20 minutes: czcams.com/video/ad4J21Pg7Bw/video.htmlsi=pASkzL2PcD6ESDrp

Yeah I've seen this same demo from twenty failed projects over as many years.

Hi doltBmB! This is described in the paper in section 3. We prevent morphing vertices by not updating the projection in each frame which results in popping vertices. With tessellation it is barely visible anymore. However, we later improved the projection technique by snapping the grid on the planets ground level to get rid of morphing and popping vertices. See our latest publication "Real-time Rendering of Procedural Planets at Arbitrary Altitudes".

Yes. If the vertices are not locked in place that will happen. However one could saturate the image with many vertices, and the effect would be deminished. What I do is move the grid in lockstep. I also expand the mesh in lockstep. But finally I juat moved dynamically creating a clipmap mesh. Not sure which is better, mine or this approach.

because clouds dont move that fast

@@UrodCyka no fast as like in this video, i know. but theyre literally standing in nasa feeds. just pick a point and mait 2min. you cant tell me clouds are don move in 2 minutes.

@@svens3722 Were they cumulus clouds because clouds at high altitude work like that. not all clouds move at the same speed thats basic knowledge

@@UrodCyka you can name what ever cloud u know. clouds dont stand 5 minutes on the same spot. and where do i get that "basic" knowledge ? in school i guess, so it have to be true. pls stop eating shit from the goverment. free your mind.

I used to live in Arizona and the skies always had little fluffy clouds in em

This paper was introducing an algorithm that could run on a GPU in real time, the implementation itself was just a protoype. Note that this paper was written over 8 years ago when real time ray tracing was a great challenge. Today I think it should be very easy and simple to implement it with hardware ray tracing (for example with Vulkan and VK_KHR_ray_query extension). If you are still interested you can check out later papers, which have algorithms implemented on a GPU and running in real time (even in VR): Image Reconstruction from Spatially Non-Uniform Samples Foveated Ray Tracing for VR Headsets

Hey, you were on the space graphics forums (it's the greater game creator)

No! Collisions are very easy for such terrains. We only need to pass the physics body's vertex closest to the center(or probably do it for each vertex on physics body if it doesn't necessarily collide from single point) and pass its coordinates to the terrain generator function. If physics body lies closer to the center of planet than value returned by function, collision detected! Beware, avoid doing complex calculations else floating point values will show there magic.

In VR? There is a FREE ONE, It is my favorite thing to relax, I go in the AIRCAR and fly around, go way above the city and look down, then zoom down to sreet level ad fly between building. If you buy an Oculus Rift S, there is a free game called: AIRCAR... There is an impanel screen you can place, that show your desktop, what I do, is put Netflix on my desktop, then in Aircar, I have a 10" tv tablet on my cockpit panel and can watch Star Trek or Friends Re-Runs while flying around making believe 'im a future cabby! www.oculus.com/experiences/rift/1204731822978255/ or search Aircar on CZcams… me-> CZcams.com/NextWorldVR I'm happy to help!

I’m pretty sure water reflection is planned and they are currently working on volumetric clouds which might be added next year

@@users4007 the water in space engine looks so bad, honestly... But clouds would add a whole new perspective...

there's a lot more info in the paper in the description, this was reak time on a GTX 1060 in OpenGL

They definitely do not need to be recalculated every frame. However, when using a quad tree for the terrain, you would need to recalculate some meshes.

Hi Ammarkhan! We are sorry to hear that. We just checked the link and it works fine within Europe. Maybe you can try finding it directly at Goolge using the following term: "Segmentation of Brain Tumors from Magnetic Resonance Images cescg pdf". At least here the paper appears as the top result. Otherwise, it could be that your region is somehow restricted to access the link, in that case you may use an endpoint in a different country for example with the help of Tor (standalone or within Brave browser) or using a VPN. Hope that helps.

@@cescg7873 Thank you .. I'll try

Dear Mahbuba, this is the channel of the scientific seminar where the student research has been published. We are not able to help you with questions about the source code, it's out of our reach. Please try ask the author via Github.

نفيذتيها؟

Hi. What you downloaded is the source code. You have to build it with a c++ compiler.

Greetings Please I did but when I qmake and make for example test.pro I have a error at the level of #include geometry/box.h ,it doesn’t exist please what should I do!?🙏🏻

Hi Alexandr, please have a look at the paper (same name as this video) in the referenced library. In case of any questions please contact the authors listed in the header of the paper.

Hi KJTR! You have to ask the Florian directly, he is the author of the software. You will find his email contact in the paper listed in the referenced library (search for the title of this video).