Jump to content

Josh

Staff
  • Posts

    22,901
  • Joined

  • Last visited

Everything posted by Josh

  1. Fixed. (It's the sphere's collider that you are seeing.)
  2. Josh

    Env var issue

    Okay, I also called SetEnvironmentVariableW and that passed the var to the child process.
  3. Debugging the VR system, I can see two separate models being loaded: indexcontroller}valve_controller_knu_1_0_right indexcontroller}valve_controller_knu_1_0_left So I am probably reusing a model twice or maybe loading them both into the same slot...
  4. I have noticed the same thing.
  5. Josh

    Env var issue

    If the ULTRAENGINE env var is not set, and you allow the editor to set it, and launch VS from the editor by opening the SLN file in the asset browser, VS will inherit the editor's env vars at launch and won't detect the new setting.
  6. Fixed. Note that your custom properties should be stored in an "extras" object: { "material": { "shaderfamily": "Shaders/PBR.fam", "texture0": "./grid01.dds", "extras": { "myproperty": 3 } } }
  7. First build of 0.9.4 on dev branch. Added View > Show Navmeshes menu item Added material pick mode in asset editor. (Engine does not load this property yet.)
  8. Use the layers parameter for depth in a 3D texture: https://www.ultraengine.com/learn/CreateTexture
  9. The lighting calculation is a bit complex in Ultra, so the shadow is checked first and if the pixel is in the shadow, that light is skipped.
  10. Wow, that is fast enough that it could be real-time. You said it takes 500 milliseconds, so if you used four threads that would go down to 125 msecs. But the whole things doesn't have to be updated all at once. You could easily cycle through and just do a limited number each frame, and a slow-moving light would look the same. Without threading, at 60 FPS it would take 30 frames to get through the entire job, so the whole thing would update twice each second. If you use Collider::Pick instead of the world raycast function, that will get rid of a lot of overhead and should be thread-safe.
  11. Josh

    Color Changer

    This uses the Quake light animation presets to add some interesting color modulation to any entity. ColorChanger.zip The following presets are available: Normal Flicker Slow Strong Pulse Candle 1 Fast Strobe Gentle Pulse 1 Flicker 2 Candle 2 Candle 3 Slow Strobe Flourescent Flicker Slow Pulse Todo: The candle presents don't look right to me, but I'm not sure what they are supposed to look like. I remember them as being a gentle flicker. There is no interpolation between the nearest two values, it just grabs one single value, so it's not very smooth. I guess this is appropriate for the strobe effects, but not for others.
  12. Works on all builds now, on Steam or standalone.
  13. Update Supports specular-gloss materials, which are often found on Sketchfab Supports unlit materials Supports occlusion textures
  14. Josh

    Thumbs

    It sounds like there is some critical error that only affects AMD cards.
  15. Josh

    Thumbs

    That is the "screenshot" command.
  16. Josh

    Thumbs

    One more question, does this command work correctly on your mchaine? https://www.ultraengine.com/learn/Framebuffer_Capture?lang=lua
  17. Josh

    Thumbs

    Here is what happens when I use this model: So I guess we can say this is an AMD issue. What card?
  18. This extension will convert all glTF textures to DDS by treating the glTF file as JSON data. Right-click on a glTF file in the asset browser, select the "Convert Textures to DDS" menu item, and the file will be modified without actually loading it as a model. This will handle animated glTF files in a non-destructive way. Convert glTF Textures.lua
  19. There is a mipmap chain error. I think this is happening because the trunk texture is a non-square image. That itself should not be a problem, it's just hitting an error in my code that isn't frequently raised...
  20. Josh

    Thumbs

    Can you upload a model that reliably causes this error?
  21. I don't understand what is happening from this description. I have never seen such behavior. Is the grid visibility problem still happening now? We are on 0.9.3, on both stable and dev branches.
×
×
  • Create New...