Jump to content

Josh

Staff
  • Posts

    23,141
  • Joined

  • Last visited

Everything posted by Josh

  1. You might want to just use the Steam build if you have any other problems.
  2. That just makes it so you have to run the installer bat file yourself. This is a security feature so you can see exactly what it is doing before you run it. If the feature is disabled then the script should just run automatically. If it needs admin permissions it will ask for it.
  3. I also see you are missing some files when the map loads. I am investigating this...
  4. Yes. Are you sure you created a Lua project? A C++ project will not have an executable until you compile it yourself in Visual Studio.
  5. Don't forget the C:\ProgramData\Ultra Engine folder
  6. Those executables do not match the ones on the Steam or standalone builds. New Project 21.rar
  7. Your project probably needs the new executables I uploaded. To get them, open the project manager and hit the sync icon.
  8. I was able to update the standalone now.
  9. This is correct on the Steam build. I am having trouble uploading the files on our server. I don't know why, I have never seen it slow like this.
  10. I think it is the file number and then the (line number).
  11. Well, in Lua there is nothing that needs to be built, but I can confirm the Lua executable is not working...
  12. What programming language are you using?
  13. I guess if you sent the light's ID to a uniform declared in the lighting file, and modified the lighting code to skip that light, but it seems difficult. Why would you want to do this? You can disable shadows on a per-light basis already.
  14. https://registry.khronos.org/OpenGL/extensions/NV/NV_mesh_shader.txt
  15. I don't know what I would do with them!
  16. 0.9.5 Lots of fixes!
  17. It actually makes sense why your colors were flipping back and forth. The bindless texture override in the shader family was not being taken into account in the sorting, so it was just random. So sometimes your trees were being rendered with the more expensive terrain shader.
  18. OpenGL 4.6 is the only renderer in version 0.9.5. I talked about it for an hour in this video: To support older hardware, I just need to write one alternative code path for systems that don't support bindless textures. OpenGL 4.6 support goes all the way back to: Nvidia GEForce 420 AMD Radeon RX 5300M Intel HD Graphics 520
  19. You can delete all thumbnails by deleting the folder C:\ProgramData\Ultra Engine\Thumbnails
  20. Okay, it will work in the build that goes up later today.
  21. I cannot fix this without the file that causes the error.
  22. I added the missing format. However, there are a few rules for terrain textures in 0.9.5 to take note of: All textures on one terrain must be the same size. There is an additional argument in the CreateTerrain function that lets you specify this size. I have not added a control in the editor yet to let you adjust the size of a terrain that is being created. The default size is 1024. Base color, metallic-roughness, and emission textures used in a terrain must be in format BC7. Displacement textures used in a terrain must be Luminance format (single channel 8 bit grayscale). Normal maps used in a terrain must be BC5 format. The reason for this is that array textures are now being used for terrain rendering. This solves the problems we were seeing with pixels on the borders invocation groups and will help make the engine runnable on a wider range of hardware. This zip file does not include any textures.
  23. I found the cause. In the visibility list, meshes are grouped by pipeline settings. This is all the different rendering settings, plus the shader in use. The pipeline settings has a < operator for sorting. This is how the grouping is done. I added a setting in the shader family to force bindless textures off, but did not add any sorting for this in the < operator in the pipeline settings class. As a result, your sphere was probably getting rendered using the terrain shader. Once I added the needed fix the problem went away.
  24. At this point I suspect a nasty memory overwrite in the terrain system. I am seeing behavior that does not otherwise make sense...
  25. This is a strange one. Has this every happened without the terrain present?
×
×
  • Create New...