Summary
On publishing a private project get Assert.digest.verse error Ambiguous module names from 29.60 when using 31.10
Please select what you are reporting on:
UEFN
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
1 find and project made in UEFN 29.30 to 30.00
2 Open in UEFN 31.00
3. Look at Verse Asset.digest.verse in VS code to bypass the read-only as a trusted source.
4. add an “s” at the end of any module name then remove this.
5. Leave VSCode Asseert.digest.verse open in the background
6. Launch project from UEFN, Validation takes place successfully so looks like working gives memory size.
7 Attempt to publish from UEFN toolbar “Project → Public Project”
8, Project Validation fails in publishing the “Asset is ambiguous” error if you are lucky!
9. Go back to your VSCode running in the background.
10. Look at the VSCode file locked and Compare errors that need attention, which means you agree to changes to 29.60 Assets. digest.verse
11. In the green background is the 29.60 version
12. In the red background is the 31.10 version
13. Wonder how long this will to fix the problem agree to these problems because you have no skill in Visual Studio 2022 17.7 Github version source control
14 Screen dump these problems for future reference below
Expected Result
Verse would provide a conversion function by putting as extra “s” at the end of the module name from 29.60 to 31.10 to make the Assert .disgest.verse compatible
Observed Result
Vscode jumps into code conflict compare mode and asks to accept changes from 29.60 to 31.10
Platform(s)
Windows UFEN Win11 and Win 10 with the latest updated Verse
Additional Notes
This Level may require Advanced requiring skill fluency in Verse or like fluency in C++
Please vote up above even if you think this is to complex to get fixed that’s Epics problem and the only way to get this fixed
#Asset.digest.verse Changes needed in 31.00 onward compare with the past pre 31.00 for example 29.60
# In the below code note the difference between "material" and Materials
#
#in the original the situation occured
#Texture := module:
# Chess<scoped {Chess}>: texture = external {}
# note how the same name has been used
From the Verse Language Quick Reference updated for 31.10 (Control + F then type “module:”
module1 := module:
module2<public> := module:
class1<public> := class {}
class2<public> := class{}
This in 31.10 Verse should be Textures
Missing comment in 29.60 to 31.00
Module import path: /ForniteCreatorName@fortnite.com.ProjectName.Texture
which should look like when updated below see the extra “s” at then end
Module import path: /ForniteCreatorName@fortnite.com.ProjectName.Textures
Textures := module:
ProjectName<scoped {ProjectName}>: texture = external {}
#the module is no longer ambiguous
#In the example below 31.10 generated Materials := module:
#in 29.60 the same line is called Material:= module:
note the extra “s” at the end of Materials which corresponds to module1 from snippet above 31.00
Module import path: /ForniteCreatorName@fortnite.com.ProjectName.Materials.ProjectName
using {/Verse.org/Assets}
Assets := module:
# Module import path: /ForniteCreatorName.ProjectName.Materials.ProjectName ( corresponds to 31.00 Asset.digest.verse)
# note the extra "s" at the end of Materials which corresponds to module1 from snippet
Materials := module:
Draws Mat<scoped {MyFeatureStand_upChair}> := class<final><public>(material):
M_Constant_material<scoped {MyFeatureStand_upChair}> := class<final><public>(material):
PLEASE Click on the Vote button at the top even if you have just seen the words “Ambiguous module names”. This is the only way to get this fixed
