andrevr
Premium
		- 909
 

- South Africa
 
For clarity, absolutely sure this doesn't apply, but ... here goesthat would be one for someone with more knowledge than I have.
The answer is DEFINITIVELY.... maybe.Would this make a track less demanding for the PC (e.g. load faster, achieve stable FPS etc.) if one hides a bunch of stuff?
Not having to render objects will always save GPU time and effort, so FPS WILL improve.
How much is the question. Noticeably? Usefully? What percentage of the "RENDER ALL" task have you mitigated?
Another consideration is that improvements are less noticeable when the engine is in the center of the performance envelope, ie, it has head-room. If the engine is at the edge of the envelope, with little or no headroom, ANY improvement might move the needle in a way that you can feel.
The only way to tell in your specific instance, is to cull a few meshes, by the method that @racinjoe013 suggested. and see if you can discern a difference. Then fact-check your feelings with CSP's very good GPU Rendering Stats app, in game.
BTW, did you know if you use the F7 camera in-game, you can fly around and inspect areas/objects, and if you have the Render Stats app open, it makes it quite easy to isolate stuff that is causing issues. Might be useful in selecting what to cull first?
Load times are unlikely to be affected. The whole KN5 must still be read in, and either kept in memory or paged. The render "Item_A" decision is made on-the-fly in-game, based on a list of notes (ext_config.ini) "Item_A = NO" = skip.
Hope this is useful.
			
				Last edited: 
			
		
	
								
								
									
	
		
			
		
		
	
	
	
		
			
		
		
	
								
							
							
						
					
					
				