Jump to content

Search the Community

Showing results for tags '2.11'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to UNIGINE Forums
    • News & Announcements
    • Getting started
  • Development
    • Content Creation
    • World Design
    • Rendering
    • Animation
    • Physics, Navigation and Path Finding
    • UI Systems
    • Sound & Video
    • Editor
    • C++ Programming
    • C# Programming
    • Networking
    • Sim IG (Image Generator)
    • VR Discussions
    • General
  • Improving UNIGINE
    • Documentation
    • Feedback for UNIGINE team
    • Bug Reports
    • Unigine SDK Beta feedback
  • Community
    • Add-on Store (https://store.unigine.com/)
    • Showcase
    • Collaboration
    • Tools, Plugins, Materials & Tutorials
    • General Discussions
  • Legacy
    • UnigineScript

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 6 results

  1. Hello Unigine :D We have a hand lag issue in Unigine 2.11.0.2 We just rebuild with “AppVarjo_double_x64” plugin (with no source code changing) but our hand having a lag issue [ Video 1 ] before before.mp4 [ Video 2 ] after (with no source code changing) after.mp4 I wonder about : Is there any confilct Varjo plugin or Leap motion plugin with Unigine And our hand having a lag issue If there’s any issue in plugin we missed, please give us a advice Thank you! our environment : Varjo XR - 3 & VR - 3 Unigine 2.11.0.2 Leap motion 4.1.0
  2. Migration 2.11 to 2.12

    Hello, I am migrating to 2.12 version right now. I fixed all api changes and changed config files from unigine.cfg to default.boot. But I am getting only a white picture for directx and opengl. We are managing opengl and directx context and application window by ourselves. Did anything change in graphics api usage? GPU usage is 100 % so it is rendering something but it is not swapping to the front buffer. Thanks
  3. Hello, I am adding reflection of wet surfaces in our application. We observed some artifacts on clouds, while rendering an environment probe with one face per frame. When switching to 6 faces per frame it looks normal, but it is too heavy in computation. What is your solution for this? There is a video in the attachement. 2020-09-04 08-51-16.mkv We did also observe that the start ray for screen space reflections gets more and more incorrect with increasing distance. It appears like the reflected object is going to vanish towards the horizon. When objects have not much space above the ground they won't appear in the reflection anyway only at close distance. Is there a way to do it more accurate than the standard project? There are two screenshot in the attachment, one far away and one close.You can see the missing plate of the material ball clearly. Software version is 2.11.0.2 Thank you for your help
  4. Hello together, I try to change the indices of an ObjectDynamic during runtime to discard some points in Unigine 2.11. I can call clearIndices() on this object and all geometry vanish. But when I change the index array and set it again. the changed data won't get uploaded and the geometry still looks the same. Any ideas? int AppWorldLogic::init() { // Write here code to be called on world initialization: initialize resources for your world scene during the world start. m_dynamicObject = Unigine::ObjectDynamic::create(); m_dynamicObject->setMaterialNodeType(Unigine::Node::TYPE::OBJECT_MESH_STATIC); m_dynamicObject->setWorldTransform(Unigine::Math::translate(Unigine::Math::Vec3(0.0, -4.0, 1.0))); m_dynamicObject->setMaterial("custom_forward_material","*"); const Unigine::ObjectDynamic::Attribute attributes[]={{ 0, Unigine::ObjectDynamic::TYPE_FLOAT, 3 }}; m_dynamicObject->setVertexFormat(attributes, 1); m_dynamicObject->setSurfaceMode(Unigine::ObjectDynamic::MODE::MODE_POINTS, 0); m_dynamicObject->setBoundBox(Unigine::BoundBox(Unigine::Math::vec3(-10000.f, -10000.f, -10000.f), Unigine::Math::vec3(10000.f, 10000.f, 10000.f))); Unigine::Math::vec3 position; for (int i = 0; i < 1000; ++i) { for (int j = 0; j < 100; ++j) { position = Unigine::Math::vec3(i, j, 1.f); m_dynamicObject->addVertexFloat(0, position, 3); } } m_indices = new int[100000]; for (int index = 0; index < 100000; ++index) { m_indices[index] = index; } m_dynamicObject->setIndicesArray(m_indices, 100000); return 1; } //////////////////////////////////////////////////////////////////////////////// // start of the main loop //////////////////////////////////////////////////////////////////////////////// int AppWorldLogic::update() { static int counter=1; if (counter % 120 == 0) { m_dynamicObject->clearIndices(); } else if(counter % 120 == 60) { for (int i = 0; i < 100000; ++i) { m_indices[i] = (rand() % 2 == 1) ? i : 0; } m_dynamicObject->setIndicesArray(m_indices, 100000); } counter++; return 1; }
  5. Hello, can you explain what this function should be doing, the documentation is not really precise on that :) https://developer.unigine.com/en/docs/2.11/api/library/lights/class.lightproj?rlang=cpp#setZNear_float_void Thanks
  6. Material migration 2.8 to 2.11

    Hello, during migration of some materials i did observe that some parameters names vanished/changed. One particular is "volume_scale", am I right it is "soft_interaction_scale" now? Are there any other names that have changed? Thanks
×
×
  • Create New...