• Advertisement
  • Popular Tags

  • Popular Now

  • Advertisement
  • Similar Content

    • By Epicghost 505
      Hello,
      We are looking for people to be apart of a team, to help create a horror game we are looking for 3d modelers, coders, artist, animators, fx artist, level designers, and audio design, there will be a payment plan once release of game                                                                                                                                                                                                                                                                                              if your interested come join our discord                                                                                                                                                                                                                                                                         We hope to see you there
      https://discord.gg/6rcc6xr
      -Epicghost505
    • By lxjk
      Hi guys,
      There are many ways to do light culling in tile-based shading. I've been playing with this idea for a while, and just want to throw it out there.
      Because tile frustums are general small compared to light radius, I tried using cone test to reduce false positives introduced by commonly used sphere-frustum test.
      On top of that, I use distance to camera rather than depth for near/far test (aka. sliced by spheres).
      This method can be naturally extended to clustered light culling as well.
      The following image shows the general ideas

       
      Performance-wise I get around 15% improvement over sphere-frustum test. You can also see how a single light performs as the following: from left to right (1) standard rendering of a point light; then tiles passed the test of (2) sphere-frustum test; (3) cone test; (4) spherical-sliced cone test
       

       
      I put the details in my blog post (https://lxjk.github.io/2018/03/25/Improve-Tile-based-Light-Culling-with-Spherical-sliced-Cone.html), GLSL source code included!
       
      Eric
    • By Octane_Test
      I am developing a mini golf game in Scenekit. I have applied dynamic physics body to the ball and static physics body to the grass surface and the brick walls show in this image.
      Issue:
      When I apply the force to the ball, the ball’s linear and angular speeds change as shown in the graphs.  The ball’s speeds don’t reduce to zero (so that the ball can stop) but remains constant after certain value.
      Ball linear speed graph
      Ball angular speed graph
      Analysis Tests:
      When I increase the values to both the rolling friction and the friction, the ball speed is reduced quickly but remains constant after certain value (similar to the above graphs). When I increase the values of the linear damping and the angular damping, the ball speed behavior is same as the point #1. When I set the gravity value to -9.8 m/s2, the ball’s linear speed remains constant after 0.1 m/s. If I reduce the gravity value to -5 m/s2, the ball’s linear speed remains constant after 0.05 m/s. The friction, linear friction, linear damping and angular damping are same throughout the motion of the ball.
      There is 1 millimeter overlapping between the ball and the surface of the golf course.
      Questions:
      From the analysis test #3, I think the gravity is causing the constant ball speed issue. Is my assumption correct? If yes, how can I fix the issue? I can’t remove the gravity field as without the gravity field the ball will not roll along the grass and it will slide. Why the friction and the damping properties are not affecting the ball speed after certain value?
      Are there any other physics properties can cause such issue?
      From the analysis test #5, are there any chances that the ball is receiving upward push to correct the position of the ball?
      Solutions:
      If I increase the physics timestep from 60 FPS to 200 FPS, the issue is resolved. I am not able to understand how this change can fix this issue? After reducing the gravity value to -1 m/s2 and physics simulation speed to 4 (4 times fast physics simulation), the issue is fixed. Again, I am not able to understand how this change fix the issue? I would appreciate any suggestions and thoughts on this topic. Thank you.
    • By stale
      I'm continuing to learn more about terrain rendering, and so far I've managed to load in a heightmap and render it as a tessellated wireframe (following Frank Luna's DX11 book). However, I'm getting some really weird behavior where a large section of the wireframe is being rendered with a yellow color, even though my pixel shader is hard coded to output white. 

      The parts of the mesh that are discolored changes as well, as pictured below (mesh is being clipped by far plane).

      Here is my pixel shader. As mentioned, I simply hard code it to output white:
      float PS(DOUT pin) : SV_Target { return float4(1.0f, 1.0f, 1.0f, 1.0f); } I'm completely lost on what could be causing this, so any help in the right direction would be greatly appreciated. If I can help by providing more information please let me know.
    • By Sandman Academy
      Downloadable at:
      https://virva.itch.io/sandman-academy
      https://gamejolt.com/games/sandmanacademy/329088
      https://www.indiexpo.net/en/games/sandman-academy
      https://www.gamefront.com/@sandmanacademy
      http://www.indiedb.com/games/sandman-academy
  • Advertisement
  • Advertisement
Sign in to follow this  

DX11 The native side of Hololens

Recommended Posts

Good time of the day, members of the forum!
    I do not think that many have tried themselves in the development under
 Hololens, but nevertheless decided to write. In any case, all work with
 Hololens is reduced to UWP and DirectX 11. So I wrote a small prototype
 for easy initialization of primitives, etc. In the scene, and began testing
 on the piece of iron ... And I was very upset by the performance tests.
       
    A short excursion, for those who are not in the subject: - the construction
of an image under Hololens, naturally a stereo image for this reason I use
 DrawInstanced with pre-prepared shaders. Shaders are very simple, conversion
 to world coordinates and projection of the species, color is set straight in
 the shader. Plus to switch the render in 2D Texture Arrays I use the geometry
 shader, that's basically all.

   For the test, I generated a grid of 10k - 30k and output them about 10
 times ... for 10k grid and 10 calls - 30fps, for the last about 18 - 20fps.
 Sadness, I thought, and I decided that my hands are not growing in size and
 my brain does not want to work anymore ...
   I decided to look for flaws in my shit ... I measured the time for drawing
10 calls - about 800 ticks, it's kind of not that bad. Slightly optimized the
sorting by materials, namely, switching between shaders minimized but in the
 loop there were updates of constant values for the shader namely transform for
each object. Fps grew by 2-3 but the time to render the frame did not measure ...
   Although Unity seems to hold the bar 1.2 - 1.3 mm triangles at 10-15 fps ...
I myself did not check the word for people.

    So, maybe someone can decide what can be crooked and what can be patched up ...

 

P.S.  The buffer of depth is 16 bit, and I use similar indices. Thank you in advance.

Edited by Deadly_kom

Share this post


Link to post
Share on other sites
Advertisement
12 minutes ago, paultrott said:

would love to read this novel prose, but it appears to be sunk into some kind of eyeFrame with annoying scrollbars

So it's better?

Here's a video with 60k triangles

Share this post


Link to post
Share on other sites

He meant not to use the 'Formatted' font (it's for code anyway), e.g. like so

Quote

Good time of the day, members of the forum!
    I do not think that many have tried themselves in the development under
 Hololens, but nevertheless decided to write. In any case, all work with
 Hololens is reduced to UWP and DirectX 11. So I wrote a small prototype
 for easy initialization of primitives, etc. In the scene, and began testing
 on the piece of iron ... And I was very upset by the performance tests.        
    A short excursion, for those who are not in the subject: - the construction
 of an image under Hololens, naturally a stereo image for this reason I use
 DrawInstanced with pre-prepared shaders. Shaders are very simple, conversion
 to world coordinates and projection of the species, color is set straight in
 the shader. Plus to switch the render in 2D Texture Arrays I use the geometry
 shader, that's basically all.
   For the test, I generated a grid of 10k - 30k and output them about 10
 times ... for 10k grid and 10 calls - 30fps, for the last about 18 - 20fps.
 Sadness, I thought, and I decided that my hands are not growing in size and
 my brain does not want to work anymore ...
   I decided to look for flaws in my shit ... I measured the time for drawing
 10 calls - about 800 ticks, it's kind of not that bad. Slightly optimized the
 sorting by materials, namely, switching between shaders minimized but in the
 loop there were updates of constant values for the shader namely transform for
 each object. Fps grew by 2-3 but the time to render the frame did not measure ...
   Although Unity seems to hold the bar 1.2 - 1.3 mm triangles at 10-15 fps ...
 I myself did not check the word for people.

    So, maybe someone can decide what can be crooked and what can be patched up ...

fixed.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Advertisement