Okay I was wrong here… It doesn’t work at runtime… Only when I close the recording app.
I tried to change the csv also manually with VS code but nothing happend it keeps the value from the previous save. So you say this is a OS problem?
Is it also possible to create a copy of the file inside UE?
Correct, this is the recording app opening the I/O stream but not closing it until it finishes recording. The OS considers the file locked while the stream is open, so other applications can’t open the file until the stream is closed.
Unreal only requests read access when loading text from a file, so that means that the recording application is requesting exclusive access to the text file and that can only be solved by editing the code of the recording application unless it has an exposed option for non-exclusive write access. Most OSes (including Windows) allow you to copy the file without the exclusion even while the file is locked, but you’ll have to handle that outside of Unreal. Unreal can make copies but only by reading the original text file and writing it to a new one, which is impossible if the file is locked with read-exclusion.
Is your recording application something custom-made or is it a software solution from a third party? @deedox
Hi Jared, thank you now it’s more clear to me…
The recording app is custom made by another dev. I will ask him to join the discussion.
Hi Jared,
I am using a NodeJS script to write data to a CSV file each second. Yes, keeping the write stream open throughout since the publishing is happening each second. Can you suggest a way to write data in a “non-exclusive” way so that Unreal can read it simultaneously ?
I am using the “a+” file system flag which allows me to both read and append the file.
There’s an exclusive flag: “ax+” too. It throws errors when we try to open a file which doesn’t exist.
“a+” automatically creates the file using the supplied file name if it doesn’t exist
While the IO write process was on, I triggered another function (process) to read the content of that file simultaneously. Was able to do so without any errors:
const {readFile} = require("fs");
readFile("./##.csv", (_err, data) => {
console.log(data.toString());
});
This also worked:
const {createReadStream} = require("fs");
const strm = createReadStream(`${__dirname}/13.csv`, {start: 0});
strm.read();
strm.on("data", (d) => {
console.log(d.toString());
})
Tested on both WIndows and macOS.
Is there a possibility that Unreal/plugin is requesting exclusive access instead?
Please let me know when you get a chance
Hello , I am trying to integrate my project from 4.26 to 4.27. In 4.26, I ran the plugin thanks to a variable named runtime data table actor. I can’t find this variable in 4.27. I guess remove it.I am sharing the problem in the screenshot. What can I put instead of runtime data table actor ?
1 Like
I don’t believe so. RDT leverages IFileManager::CreateFileReader with no flags. Looking at the code in the implementation, it doesn’t have any code I can sniff out that requires exclusivity or write access (which is something defined in the flags parameter).
Is there any way you can write to a new file on each loop or close the write stream between writes?
Hello emincelik, the actor that controlled these operations has been replaced with a UObject to allow for operations to complete at design time, not just runtime. But everything that you could do with the actor can now be done with just the CSV Info. From your screenshot, it looks like you’re just checking the validity of the actor then destroying it - is there anything else you’re using it for that you need some help with finding an alternative?
Creating a new copy of the original CSV each second also didn’t work. Perhaps the default (no flag) indicates exclusivity? The thing is that when a custom script is used to read the CSV simultaneously it works. If the recorded app was requesting exclusive access that should have failed too
Would you be able to send me the recording program with some mock data? It’s not possible to debug this without a repro at this point. I’ll need to step through the code but I don’t have a way to trigger this issue.
Hi Jared,
Great plugin - any chance you could update the code to remove the deprecation warnings? I know these are only deprecation warnings in prep for 5.1 and thus doesn’t necessarily need addressing immediately. However, it would be nice to stop these warnings appearing during output logs for code compiles + project packaging.
Many thanks,
Hello AgentMilkshake1,
I totally understand not enjoying all those deprecation warnings - I definitely don’t either! But they are important because 1) It stops new users from being able to access those functions and 2) It helps existing users update their code to the new functions.
Now the reason that you’re seeing it so much when packaging is because of the OneNode struct that was used to pass information around in the old style workflow. This whole workflow has been deprecated now but was the only way to get anything done previously so a LOT of users are still using this code. Therefore I can’t just remove it immediately. Many people would be upset that their code stopped working when they thought they had until 5.1 to fix it!
So I’m sorry but I’ve got to stick to my guns here. It sounds like you have some C++ skills though, so an easy fix in your situation would be:
- Move Runtime DataTable from {Engine}/Plugins/Marketplace to your project’s Plugins folder
- Go to line 134 in Plugins/RuntimeDataTable/Source/RuntimeDataTable/Public/RuntimeDataTable.h
- Remove the UE_DEPRECATED macro between “struct” and “FOneNodeInfoStruct”
- Compile
That should take care of all but two warnings. If you want to take care of the rest, you can just remove all deprecation warnings (or all deprecated functions if you’re so inclined).
1 Like
Hey Jared,
No problem! I didn’t take a look into the deprecation warnings and therefore wasn’t aware they related to vital functionality still required by existing users!
Totally understandable why these still warnings still exist.
Many thanks for the swift reply!
Glad to offer perspective! They will all be gone by 5.1, so please bear with me until then!
Hello, i recently acquired the plugin however i have had some difficulties getting it to work with C++
Whenever i have FEasyCsvInfo variable marked with UPROPERTY() the engine will fail to compile with the following error
error LNK2019: unresolved external symbol "__declspec(dllimport) class UScriptStruct * __cdecl Z_Construct_UScriptStruct_FEasyCsvInfo(void)
I alredy added RuntimeDataTable to my .Build cs files on my PrivateDependencies, im also including the relevant headers on my class (EasyCsv.h )
If i remove the UPROPERTY macro it compiles correctly however i need to expose an FEasyCsv struct to my C++ classes
Hey alvarokw, Easy CSV is its own module now, not in the same module as RuntimeDataTable. You’ll need to add easyCSV to the Private/Public dependencies as well.
For some reason, I need to use UE 4.23. I had successfully use your plugin on 5.0 but I could not get it to work on 4.23.
This is my setup:
When I play in the editor, this is the result:
The google sheet URL is already set to anyone with link can view.
I do see a difference in the node between your sample video and my Fill Struct from Google Sheets or Local CSV node. Mine do not have the API Key. I am not sure what else I might be missing.
Hello Tracy_HTech, welcome to the forums!
Your setup looks correct! I see you are printing the payload already. What is the payload exactly?
Can you look inside the Runtime DataTable Actor and see if there’s anything in the Csv Info?
Hi, It wasn’t printing any payload. I was checking the length of the S_RDTDATA array (which is the struct array to fill) and the length came out 0 (print string in blue 0). And checking on the Call on Complete event (OnDataFillComplete) whether its successful, it went to false, hence the print string of Failed in blue.