• Advertisement
  • Popular Tags

  • Popular Now

  • Advertisement
  • Similar Content

    • By turanszkij
      Hi,
      I finally managed to get the DX11 emulating Vulkan device working but everything is flipped vertically now because Vulkan has a different clipping space. What are the best practices out there to keep these implementation consistent? I tried using a vertically flipped viewport, and while it works on Nvidia 1050, the Vulkan debug layer is throwing error messages that this is not supported in the spec so it might not work on others. There is also the possibility to flip the clip scpace position Y coordinate before writing out with vertex shader, but that requires changing and recompiling every shader. I could also bake it into the camera projection matrices, though I want to avoid that because then I need to track down for the whole engine where I upload matrices... Any chance of an easy extension or something? If not, I will probably go with changing the vertex shaders.
    • By NikiTo
      Some people say "discard" has not a positive effect on optimization. Other people say it will at least spare the fetches of textures.
       
      if (color.A < 0.1f) { //discard; clip(-1); } // tons of reads of textures following here // and loops too
      Some people say that "discard" will only mask out the output of the pixel shader, while still evaluates all the statements after the "discard" instruction.

      MSN>
      discard: Do not output the result of the current pixel.
      clip: Discards the current pixel..
      <MSN

      As usual it is unclear, but it suggests that "clip" could discard the whole pixel(maybe stopping execution too)

      I think, that at least, because of termal and energy consuming reasons, GPU should not evaluate the statements after "discard", but some people on internet say that GPU computes the statements anyways. What I am more worried about, are the texture fetches after discard/clip.

      (what if after discard, I have an expensive branch decision that makes the approved cheap branch neighbor pixels stall for nothing? this is crazy)
    • By NikiTo
      I have a problem. My shaders are huge, in the meaning that they have lot of code inside. Many of my pixels should be completely discarded. I could use in the very beginning of the shader a comparison and discard, But as far as I understand, discard statement does not save workload at all, as it has to stale until the long huge neighbor shaders complete.
      Initially I wanted to use stencil to discard pixels before the execution flow enters the shader. Even before the GPU distributes/allocates resources for this shader, avoiding stale of pixel shaders execution flow, because initially I assumed that Depth/Stencil discards pixels before the pixel shader, but I see now that it happens inside the very last Output Merger state. It seems extremely inefficient to render that way a little mirror in a scene with big viewport. Why they've put the stencil test in the output merger anyway? Handling of Stencil is so limited compared to other resources. Does people use Stencil functionality at all for games, or they prefer discard/clip?

      Will GPU stale the pixel if I issue a discard in the very beginning of the pixel shader, or GPU will already start using the freed up resources to render another pixel?!?!



       
    • By Axiverse
      I'm wondering when upload buffers are copied into the GPU. Basically I want to pool buffers and want to know when I can reuse and write new data into the buffers.
    • By NikiTo
      AMD forces me to use MipLevels in order to can read from a heap previously used as RTV. Intel's integrated GPU works fine with MipLevels = 1 inside the D3D12_RESOURCE_DESC. For AMD I have to set it to 0(or 2). MSDN says 0 means max levels. With MipLevels = 1, AMD is rendering fine to the RTV, but reading from the RTV it shows the image reordered.

      Is setting MipLevels to something other than 1 going to cost me too much memory or execution time during rendering to RTVs, because I really don't need mipmaps at all(not for the 99% of my app)?

      (I use the same 2D D3D12_RESOURCE_DESC for both the SRV and RTV sharing the same heap. Using 1 for MipLevels in that D3D12_RESOURCE_DESC gives me results like in the photos attached below. Using 0 or 2 makes AMD read fine from the RTV. I wish I could sort this somehow, but in the last two days I've tried almost anything to sort this problem, and this is the only way it works on my machine.)


  • Advertisement
  • Advertisement
Sign in to follow this  

DX12 Matali Physics 3.8 Introduces Deformable Triangle Meshes And Advanced Destruction

This topic is 697 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

We are pleased to announce the release of Matali Physics 3.8, version which introduces significant functional enhancements.

 

What is Matali Physics?
 
Matali Physics is a high-performance, rock-solid stable, advanced 3D physics engine intended for physics-based simulations and games. The engine comes in three editions and is available across multiple platforms:

  • Android
  • BlackBerry OS
  • *BSD
  • iOS
  • Linux
  • OS X
  • SteamOS
  • Windows 10 UAP/UWP
  • Windows 8/8.1/10 Desktop
  • Windows XP/Vista/7

 

What's new in version 3.8?
 

  • Deformable triangle meshes. This functionality makes possible real-time deformation of triangle meshes together with full collision detection;
  • Advanced modeling of objects destruction process. This functionality significantly simplify implementation and control of objects destruction, while providing high performance and realism of the simulation. Currently, each group of physics objects can disintegrate spectacularly in a manner defined by the designers;
  • A more flexible model of collision groups;
  • Matali Render 2.5 add-on with comprehensive support for tangent space needed for effects such as normal mapping and related techniques. Support for the tangent space is ready for both the high-level programmable APIs and DirectX 12.

         more...

 

s32.jpg

 

Main benefits of using Matali Physics:

 

  • Stable, high-performance solution supplied together with the renderer and content pipeline for all major mobile and desktop platforms (both 32 and 64 bit)
  • Advanced samples ready to use in your own games
  • New features on request
  • Dedicated technical support
  • Regular updates and fixes

 

s22.jpg

 

The engine history in a nutshell

Matali Physics was built in 2009 as a dedicated solution for XNA. The first complete version of the engine was released in November 2010 and it was further developed to July 2014 forming cross-platform, fully manage solution for .NET and Mono. In the meantime, from October 2013 to July 2014 was introduced simultaneous support for C++. A significant change occurred in July 2014 together with the release of version 3.0. Managed version of the engine has been abandoned and the engine was released solely with a new native core written entirely in modern C++. Currently, the engine is intensively developed in C++ as an advanced cross-platform physics solution.
 

If you have questions related to the latest update or use of Matali Physics engine as a stable physics solution in your projects, please don't hesitate to contact us.

Share this post


Link to post
Share on other sites
Advertisement
Sign in to follow this  

  • Advertisement