That would depend on what you are testing, and if you are changing code. If your changing blueprints, or C++ your going to need to rebuild. If your only testing, how the “data” that you refer too is impacting the code, then only that should need to be changed. If your testing changes to a 3rd Party Library, only the library would need to be changed, if you are loading the library itself, and not integrating it into the “game” itself.
But without a clear definition of the “data” that you reference, it’s hard to give a more clear answer. Bottom line is, whatever your changing, will need to be rebuilt.
I’ll be developing an AR app for mobile devices that support ARKit / ARCore.
My question is, every time I wish to test a change or toubleshoot something, do I have to re-build the whole project and re-deploy it on my device? Is there a possibility, to somehow feed the data from the mobile device back into the engine and just rapidly prototype things, without the massive downtime each time I wish to test a change?
Yes, I also would like to know about possible ways to emulate AR on PC. Currently, I do a small change and compiling it for 30 min to preview this change and then I move on again. It takes a long time in production.