The documentation indicates that the Dollycam path files should be stored in {RL folder}/bakkesmod/data/campaths/filename.json. However, at least as of Bakkesmod 86(? Not sure how to get version, just know I'm running latest and that's the last commit to the SDK repo), the files don't seem to be going here. Instead, I'm finding the files are being saved in {RL folder}Binaries/Win32. Interestingly enough, the files are also being saved without the .json extension.
Despite this, it seems like the plugin is saving/loading paths correctly, so I wouldn't necessarily call this a bug so much as an unexpected/undocumented behaviour.
Seems like there's not actually any logic to add the .json extension in the event that the user hasn't provided it (again, that's fine, I think we can expect that anyone who's digging around here probably knows how to open a JSON file without an extension, but for editors with syntax highlighting and other niceties, it might be nice to do it anyway).
It also seems like -- and I don't know jack about C++ so pardon me here -- the working directory context of the plugin might've changed somehow since this commit, due to changes to RL or the Bakkes SDK or whatever, and so now perhaps the subdirectory of ./bakkesmod/data/campaths should be prepended to filename? I'd submit a PR, but I'm afraid I'd just be ignorantly patching a context issue symptom that might need to be handled somewhere else in a more general way.
Hey there.
The documentation indicates that the Dollycam path files should be stored in
{RL folder}/bakkesmod/data/campaths/filename.json
. However, at least as of Bakkesmod 86(? Not sure how to get version, just know I'm running latest and that's the last commit to the SDK repo), the files don't seem to be going here. Instead, I'm finding the files are being saved in{RL folder}Binaries/Win32
. Interestingly enough, the files are also being saved without the.json
extension.Despite this, it seems like the plugin is saving/loading paths correctly, so I wouldn't necessarily call this a bug so much as an unexpected/undocumented behaviour.
Starting on line 125 of
dollycamplugin.cpp
:Seems like there's not actually any logic to add the
.json
extension in the event that the user hasn't provided it (again, that's fine, I think we can expect that anyone who's digging around here probably knows how to open a JSON file without an extension, but for editors with syntax highlighting and other niceties, it might be nice to do it anyway).It also seems like -- and I don't know jack about C++ so pardon me here -- the working directory context of the plugin might've changed somehow since this commit, due to changes to RL or the Bakkes SDK or whatever, and so now perhaps the subdirectory of
./bakkesmod/data/campaths
should be prepended tofilename
? I'd submit a PR, but I'm afraid I'd just be ignorantly patching a context issue symptom that might need to be handled somewhere else in a more general way.