I'm just running into one error after another here. But this seems unrelated to my pre

EDIT: Looking into a little closer. Commit <a class="commit-link" dat

Crash due to body material not being available on start about regoth-bs HOT 6 OPEN

Nutomic commented on August 22, 2024

Crash due to body material not being available on start

from regoth-bs.

Comments (6)

ataulien commented on August 22, 2024

Interesting. Looks like the players body material has not been copied. That error is also thrown for handles which did not ever point to a valid object, so most likely Destroyed is not correct here, but that's an other issue! 😄

Can you delete bin/cache/* and try again? Maybe the player model got corrupted because of a crash while caching resources...

I'll take a look at it when I get home!

PS: I would suggest changing the issue title to "Crash due to body material not being available on start" or something...

from regoth-bs.

Nutomic commented on August 22, 2024

I already retried it with a cleared cache a few times, but the same error always happens. And I updated the title, but you can also do that yourself ;)

from regoth-bs.

ataulien commented on August 22, 2024

There are some other executables, such as REGothCharacterMovementTester. Does that work?

from regoth-bs.

Nutomic commented on August 22, 2024

I tried REGothCharacterMovementTester, it has the exact same error (with cleared cache). REGothWorldCacheTest, REGothWorldMeshViewer and REGothCharacterViewer seem to work (there are no errors).

from regoth-bs.

KirmesBude commented on August 22, 2024

EDIT: Looking into a little closer. Commit e080948 was a bugfix so it works from cache, but the two lines in VisualCharacters onInitialized are always executed even if the objects are not loaded.

I am running into the same problem.
From my quick research at the point where setBodyTexture is called

REGoth-bs/src/components/VisualCharacter.cpp

Lines 40 to 46 in 408a0db

 void VisualCharacter::onInitialized() 

 { 

 VisualSkeletalAnimation::onInitialized(); 

 setBodyTexture(mBodyState.bodyTexture); 

 setHeadTexture(mBodyState.headTexture); 

 }

The mSubRenderable has not been initialized yet

REGoth-bs/src/components/VisualSkeletalAnimation.cpp

Lines 26 to 38 in 408a0db

 void VisualSkeletalAnimation::onInitialized() 

 { 

 bs::Component::onInitialized(); 

 if (mSubRenderable) 

 { 

 // If this is called after deserialization, we need register the event-callback in here 

 setupAnimationComponent(); 

 // Also the materials need to be cloned again, as those resources were not saved. 

 cloneMaterials(); 

 } 

 }

I dont know enough about the component, but maybe it is enough to call buildObjectSubtree in the onInitialize function.

from regoth-bs.

ataulien commented on August 22, 2024

When onInitialized is called, the Visual does not even know what it should be drawing if I'm not mistaken. The subtree is only built after a visual has been assigned. We should rather guard the calls which set the textures by whether a head and/or body mesh exists IMHO.

from regoth-bs.

Crash due to body material not being available on start about regoth-bs HOT 6 OPEN

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	void VisualCharacter::onInitialized()
	{
	VisualSkeletalAnimation::onInitialized();

	setBodyTexture(mBodyState.bodyTexture);
	setHeadTexture(mBodyState.headTexture);
	}

	void VisualSkeletalAnimation::onInitialized()
	{
	bs::Component::onInitialized();

	if (mSubRenderable)
	{
	// If this is called after deserialization, we need register the event-callback in here
	setupAnimationComponent();

	// Also the materials need to be cloned again, as those resources were not saved.
	cloneMaterials();
	}
	}