Amerio.Stephane Posted November 6 Share Posted November 6 Hi, my slave crashes consistently when receiving a DIS entity on the master (2.19): D:\BA\work\88ad9be9b48cc9ce\source\ig\ig\systems\Entity.cpp:1648: Assertion: 'entity' Plugins loaded are IG, CIGI and DIS connectors on the master, just IG on the slave. Link to comment
mifril Posted November 7 Share Posted November 7 Hi! Could you please clarify what exactly you are doing, what is your configuration, and attach the assert call stack, any information you can share, the logic you are using, or the data would not be a problem. Link to comment
Amerio.Stephane Posted November 7 Author Share Posted November 7 Well, pretty easy to reproduce: create a new IG project, cpp copy launch_debug.bat into launch_debug_slave.bat in launch_debug.bat, add UnigineIG,UnigineCIGIConnector,UnigineDISConnector and -sync_master 1 -sync_allow_extra_slaves 1 in launch_debug_slave.bat, add UnigineIG and -sync_master 0 launch both master and slave start a CIGI emitter to load database 1 start a DIS emitter to send any entity slave goes boom I guess the path is somewhere on some developer's desktop of yours :) 1 Link to comment
Amerio.Stephane Posted Monday at 03:31 PM Author Share Posted Monday at 03:31 PM So, do you confirm this bug ? Link to comment
silent Posted Tuesday at 04:54 AM Share Posted Tuesday at 04:54 AM I've sent you PM yesterday with our steps, no crash so far. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Amerio.Stephane Posted Tuesday at 02:30 PM Author Share Posted Tuesday at 02:30 PM Oh I HATE this kind of random_or_PC_specific bugs :( Changed PC and couldn't reproduce either; checked back on first PC and recreated the project: crash again this morning but *same project* works OK 2h later. What on earth could trigger this? Can it be related to the network activity, drivers, antivirus, firewall??? Link to comment
silent Posted Tuesday at 04:12 PM Share Posted Tuesday at 04:12 PM If you are on Intel CPU from this list: 13700 / 13900 / 14700 / 14900 - it's better to update your motherboard BIOS to the latest available revision. There are huge instabilities reported on these hardware. However, BIOS update would not help if your CPU die is physically damaged on factory. In that case RMA is only option. If there is a stable reproduction - we can track down and fix the issue, especially if it's related to the engine side. But so far we were unable to get any crashes with DIS on our side. You can also try to install the latest MSVC redist packages, just in case: https://aka.ms/vs/17/release/vc_redist.x64.exe How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Lales.Charles Posted Tuesday at 05:09 PM Share Posted Tuesday at 05:09 PM Hi, FYI, we updated the machine with all Dell drivers and seems fine now. Also NVIDIA very last studio driver. Regards, Charles 1 Link to comment
Recommended Posts