Open TheDude53 opened 2 years ago
Probably your hardware cant keep up
Possibly. What are your GPU specs (for comparison)?
intel i7 4770, its intergraded intel hd 4600 and 8gb ram
I've been managing to reproduce this issue consistently by spawning multiple (two or three) USS Gerald R. Ford ships. On a Release build it crashes a couple seconds after spawning in he second/third ship, however on Debug I get an assert the moment I hit Enter at the selector.
Back trace, hopefully it helps:
> RoR.exe!std::vector<RoR::PointColDetector::kdnode_t,std::allocator<RoR::PointColDetector::kdnode_t>>::operator[](const unsigned __int64 _Pos) Line 1747 C++
RoR.exe!RoR::PointColDetector::queryrec(int kdindex, int axis) Line 153 C++
RoR.exe!RoR::PointColDetector::queryrec(int kdindex, int axis) Line 191 C++
RoR.exe!RoR::PointColDetector::query(const Ogre::Vector<3,float> & vec1, const Ogre::Vector<3,float> & vec2, const Ogre::Vector<3,float> & vec3, const float enlargeBB) Line 147 C++
RoR.exe!RoR::ResolveIntraActorCollisions(const float dt, RoR::PointColDetector & intraPointCD, const int free_collcab, int * collcabs, int * cabs, RoR::collcab_rate_t * intra_collcabrate, RoR::node_t * nodes, const float collrange, RoR::ground_model_t & submesh_ground_model) Line 229 C++
RoR.exe!RoR::Actor::CalcCabCollisions() Line 2418 C++
RoR.exe!RoR::Actor::CalcForcesEulerCompute(bool doUpdate, int num_steps) Line 62 C++
RoR.exe!RoR::ActorManager::UpdatePhysicsSimulation::__l16::<lambda_1>::operator()() Line 1092 C++
[External Code]
RoR.exe!RoR::ThreadPool::{ctor}::__l2::<lambda_1>::operator()() Line 157 C++
[External Code]
Steps to reproduce
Expected behavior
RoR shouldn't crash. If it must, it should give a reason.
Actual behavior
RoR crashed and RoR.log did not provide any reason (as shown below)
System configuration
OS: Windows 10 21H1 64bit Renderer used: DirectX 9 CPU: 11th Gen Intel® Core™ i5-1135G7 GPU: Intel® Iris® Xe Graphics (driver version 30.0.100.9955)
Additional information, logs and screenshots (optional)
The end of RoR.log