So I have an open world map that I’m adding a bunch of grass to, and all seems well except one issue- When the grass is close to the camera it looks really weird. You can see this in the screen shot below: [cropped] However, in this playground the issue does not seem to happen: Babylon…

Woah, nice tool, I’ll try that out. I’ll also try to get this up live, I was only just starting to play with adding grass to my map; I’ll move quickly to just have it added to the areas around the base of each tree using that same algo I used in the playground. The live demo itself is here: https:/…

@Evgeni_Popov Unfortunately I won’t be able to work on this till Tuesday probably. I realized I need to use some precomputed results regarding the placement of each grass instance, and doing that right will take a little more time.

@Evgeni_Popov btw, I had another tangential question regarding thin instances I was hoping to ask you- if I have 140k grass model thin instances but I want to reduce the burden on the gpu, if I were to set the scaling to zero for all thin instances not located in the players current grid region on …

Yes, it would reduce the burden a bit because the triangles with vertex scaling = 0 would have no area so the fragment shader will never be executed for them. You could reduce the burden even further by making sure those triangles have 0 area at the geometry level: you can do this by copying the 2nd…

So I tried out turning off the grass thin instances via setting scaling to zero, and turning those thin instances back on again via the reverse operation of setting their scaling back to it’s original value. Unfortunately it takes a really long time to do so. To solve this issue of wanting to have …

[image] arcman7: I would then create thin instances that pertain to a given region and have the visibility of that grid’s source mesh toggled on and off This strategy looks good to me as long as your grid cell is big enough (if the source mesh has only 5 thin instances it’s probably not inter…

[image] Evgeni_Popov: This strategy looks good to me as long as your grid cell is big enough (if the source mesh has only 5 thin instances it’s probably not interesting), as your grid is already your visibility unit. Each grid’s source mesh for the grass would be responsible for ~ 1400 - 1600…

Okay, so this approach seems to be performing a bit better, but I’m still hitting an issue: Map.ts:651 ** setCurrGridZone - calling _loadGrid 10 6 setCurrGridZone @ Map.ts:651 onPlayerMoveCallback @ Game.ts:971 _updateFromKeyboardControls @ Player.ts:793 _beforeRenderUpdate @ Player.ts:984 notifyOb…

Are you sure you have enough data in the thin instance buffers to account for mesh.thinInstanceCount instances?

I think so… here’s how I load a given grid: _loadGrid(row: row, col: col) { /* grid[row][col] = return value of getGridResourceTemplate */ const grid = this._eeResourcesGrid[row][col] console.log('loadGrid: ', grid) for (const [_eeName, eeResource] of Object.entries(grid)) { …

Weird pixelized coloring near camera

Questions

arcman7 October 24, 2022, 7:44pm 15

@Evgeni_Popov I think it has to do with this

Topic		Replies	Views
Field of grass? Questions	41	5809	May 21, 2024
Quest to create a Hologram with a JPEG! (how to? using Thin Instances, Matrix, Arrays) Questions documentation , material	116	4331	February 13, 2022
Problem of Thin Instance Questions thininstances	5	132	August 28, 2024
How to achieve grass "3d effect" similar to this one Questions	82	1508	August 10, 2024
[Performance] What is eating up frametime in this scene with only simple 3d hexagon meshes? Questions performance	31	2170	November 17, 2021

Weird pixelized coloring near camera

Related topics