Closed Kein closed 9 months ago
this only works on Fortnite.
Haha what
JsonAsAsset only works on Fortnite. It will not work on RoboCop you idiot.
JsonAsAsset only works on Fortnite.
"LOL", said scorpion, "LMAO even".
JsonAsAsset only works on Fortnite. It will not work on RoboCop you idiot.
It's a data table you idiot. Only materials and material functions are exclusive to Fortnite
Have you setup the Data Table class in C++? What is the name? Can we see it? Provide more context and description and a sample of the file, we can't help you otherwise.
Have you setup the Data Table class in C++?
It is mentioned in my opening post.
Name of what would you like? And what sample file do you need? You want me to upload DT asset and share on GH? You sure this is a good idea for the repo well-being given the publisher name?
I can share JSON data itself, probably? DT_FPPRifleSettings.json
Have you setup the Data Table class in C++?
It is mentioned in my opening post.
Name of what would you like? And what sample file do you need? You want me to upload DT asset and share on GH? You sure this is a good idea for the repo well-being given the publisher name?
I can share JSON data itself, probably? DT_FPPRifleSettings.json
Man, I'm trying to help you, not trying to start a stupid fight. I was simply asking just to clarify some details.
I'll take a look at the JSON file once I get home to see what could be causing issues, so don't worry.
Have you setup the Data Table class in C++?
It is mentioned in my opening post.
Name of what would you like? And what sample file do you need? You want me to upload DT asset and share on GH? You sure this is a good idea for the repo well-being given the publisher name?
I can share JSON data itself, probably? DT_FPPRifleSettings.json
Looking at the code it seems to be that your Local Fetch API seems to be not responding to plugin, recheck your settings and try again.
it seems to be that your Local Fetch API seems to be not responding to plugin,
Elaborate what does that mean, it clearly sent and received response and crashed on that reponse.
If you take a look at the line of code it crashed on, it gets "jsonOutput" from the response of the api, which it crashes while doing so. Leading to the conclusion that the API responded a invalid request.
Okay and how I'm supposed to fix it? I see in the TCP trace that there is an exchange:
Here are the settings for posterity:
[/Script/JsonAsAsset.JsonAsAssetSettings]
ExportDirectory=(Path="D:/Programs/Fmodel/Output/Exports")
bAllowPackageSaving=True
bSkipResultNodeConnection=True
bEnableLocalFetch=True
UnrealVersion=GAME_UE5_2
MappingFilePath=(FilePath="D:/Unreal/_Mappings_/RoboCop-Win64-Shipping.usmap")
ArchiveDirectory=(Path="e:/Steam/steamapps/common/Robocop/Game/Content/Paks")
bChangeURL=True
Url="http://127.0.0.1:1500"
I also can send and receive response from 127.0.0.1:1500 when it is being listened to.
In what way it is fixed?
There has been no usable information provided to work towards a fix. So it has been closed until such info is provided.
What information do you possibly need? I gave you name of the game, all the configuration data and described the issue. Am *I* supposed to know what is missing when the tool does not work as described?
I don't appreciate you being rude. Considering it's an isolated issue as it has been reported by no-one else, and it's unreproducible by either me or Tector, you would need to debug it yourself to find where exactly the issue lies. Considering you have said that the API functions properly separately, it leads me to believe it's related to your local firewall, but I've never seen it cause a disconnect between programs.
Windows Firewall never blocks locahost
connections, nor outgoing, nor ingoing. This kind of rule has to be explicitly added and it is non-trivial. Taking into account the fact all other tools and apps that use localhost
work just fine - this is not an issue of the firewall.
More than that, in the screenshot of the TCP trace above you clearly can see UnrealEditor.exe
and JsonAsAsset.exe
exchanged 213-262 bytes of data successfully. So the connection worked.
So again, you need to debug it yourself to find exactly where the issue lies, as you said yourself there is a connection made. If you could provide an updated crash log with the latest plugin, I'll take a final look over.
I've tested latest version on 5.3.0 - STILL the same issue is observed (on a simple CurveTable)
Using Robocop: Rogue City demo as a base and current
master
branchCrash log:
JASAPI log: