[MAJOR] Asset Reflection

General Issues and Bug Reporting
, ,
47

happening to me too

48

FORT-920635 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 36.00.

49

The idea is that enabling Scene Graph should work similarly to updating your project’s Verse language version- it’s something you probably want to do eventually, but you should be able to do it on your own terms only if and when you want that new functionality. It should never be forced on like it was here.

50

Hi @underthebridgeDC and @Breast, sorry to hear you’re still running into issues. Could you post your editor logs from when you experienced the crash? This will help us in terms of investigating. Thanks.

51

Hi, I need help with this, please. I haven’t been able to find a solution for a month.

52

Im still having issues with this and it wont let me publish my project now

53

same here, not being able to publish.

Here’s what’s in my .uefnproject file:
“experimental”:
{
“sceneGraph”:
{
“bIsSceneGraphSystemAllowed”: true,
“bEnableOneFilePerEntity”: false
},
“experimentalContent”:
{
“bIsExperimentalContentAllowed”: false
},
“version”: 1,
“inventory”:
{
“bIsCustomInventoryAllowed”: false
},
“physics”:
{
“bShouldEnableToggle”: true,
“bIsExperimentalPhysicsEnabled”: false
},
“sceneGraphExperimentalFeatures”:
{
“bAreSceneGraphExperimentalFeaturesAllowed”: false
},
“scriptableTools”:
{
“bIsScriptableToolsEnabled”: false
}
},

54

Hi @hellobard ,
This needs to be manually edited in Notepad to false

“bIsSceneGraphSystemAllowed”: false,

hi [
@russell.johnston
](russell.johnston | Epic Developer Community
Looks like this has a regression. Its back in 36.20

55

This doesnt work for me since the last update

56

Won’t this disable SceneGraph? I’m using SceneGraph beta features in the project.

57

hi @hellobard ,
Thats ok as long as you dont want to publish anything!. Its experimental!

58

Scene Graph is in beta. Telling people using SG to ‘just disable it’ is not a solution.

59

Yeah I dont know why disabling something that should be fine to publish is a “fix” We need to find out why this is actually happening because the fix that they gave us will not work

60

We are back to experiencing this issue once again in our map.

We originally solved this issue in a previous update using the .uefnproject and .uplugin file editing method outlined above.

We do not have any experimental features enabled in the project settings.

image
image664×350 42.7 KB

61

Hi there. Unfortunately, we are aware of a bug where even if you do not explicitly check [Scene Graph Experimental Features] in the project settings, as long as [Scene Graph System] is checked, you will not get explicit Verse compilation errors locally in the editor, which would have alerted you that you were making use of definitions that are marked as @experimental. From looking at your project specifically, there were multiple @experimental definitions being made use of in your project’s Verse sources, including:

scene_event, fort_guard_perception , fort_guard_alert_level , fort_npc_perception , fort_target_info , (entity:)SendUp , GetFortGuardPerception , AlertLevelChangedEvent , GetFortNPCPerception , TargetSeenEvent

among others. If you remove the usage of these experimental definitions, you should then be allowed to publish the new version.

We do want to expose this sort of information in a better way than it is right now, where you can’t see what the problematic definitions (or code making use of said definitions) are.

2 Likes
62

Are you saying I cannot publish my game because I use .GetEntity???

image

image
image643×204 7.57 KB

63

@BenPen: Any usage of any @experimental definition will currently block you from publishing your project, correct.

1 Like