3 minutes ago, GoliathForge said:

you can drill into those functions to get tighter detail (double click)

Ok, for example this window here(cpusample image) (using the CPU sampling method):

It only shows one of my engine functions as hot, the rest are system dlls, the function is a software call to draw a bitmap, when double clicking it opens the code, it tells me that Present function is taking up most of the time. I'm not really seeing a realistic bottleneck to cause 80 fps framerates.

I just want to conclude with something definitive, so everyone agrees that it's normal for the performance to drop 1300% when switching to wireframe mode? 

Edit: Also what are some solutions to this? If I want to overlay wireframe over the models, or if I want to use wireframe at any point in the renderings, is there some kind of custom solution that I have to write, a shader or something like that? Is there anything available already?

2 minutes ago, Gnollrunner said:

Here's a vid I can put in a tri counter if you're really interested. Should only take a few minutes. I Even zoomed in where my frustum culling is dong a lot more work, I'm still getting over 900 fps.  You would think it should be a lot faster in wire frame since the vast majority of pixel shaders don't have to run and they are simple shaders at that.

2019-05-18_00-23-21.mp4

So what gives? That model looks like it has 3x as many ponys as mine

39 minutes ago, Gnollrunner said:

Don't know. I just turned off wire frame. It looks like a blob since I'm still working on my lighting system (ha, ha) but it does run a tad faster without wire frame.  However it's not more than 10% difference, maybe 7%.  Maybe it has to do with the way DX11 does culling in different rendering modes. When I  hadn't implemented my frustum culling yet and I was zoomed in, the frame rat dropped to under 20 FPS.  I guess that made sense since the CPU was dong a lot of wasted calls to the GPU. But maybe they have optimized the hell out of shaded culling and didn't bother with wire frame since it's generally for debugging.  I really don't know. I'm just spitballing .

I'm looking for frustrum culling settings, where can I check if it's enabled? Maybe that's the issue? Also what is that blob? It looks interesting. Is that some kind of adaptive tessellation? Can you just give a brief on what tech/libraries you're using?

40 minutes ago, Green_Baron said:

Just for completeness. In my case the framerate drops by 50%. But it is a gtx 970 and my skills do leave room for improvement :-/. For example, i could combine more drawcalls ...0

 

That looks like a very dense mesh, what framerates is it running at? I'd gladly take the 50 % drop over what I have now (1300% drop). I think you mentioned it earlier, could it have something to do with frustrum culling? I've checked the setting and don't see myself explicitly enabling it aanywhere in the code, maybe I'm not using it and that's causing the issue? Also, that's a pretty nifty terrain, did you write all the code yourself and if you can share what tech/libraries you're using and just explain your project in general?

28 minutes ago, Gnollrunner said:

 

  

 I'm not using anything other than DX11 and C++. It's a procedural voxel planet.  I guess it's a planet engine of sorts.  It runs off of simplex noise, but I'll add other functions later.

The blogs looks really interesting. Does this require tons of math? I'm working on terrain myself at the moment and even the basic things like getting heights of the terrain at the player position took me lots of time just to find the formulas etc. What kind of a background do you have, if you don't mind me asking?