@theonecalledtom: Yes, I tried and I’m getting Code 301 in response.
@
I don’t think I’ve hit this one. Perhaps an issue with your url?
As I say I might be able to look into providing updated code next week. Not sure that I’ve changed anything that affects s3, however I do have fixes for other services (SQS, SES whatever).
URL is working. It seems to be related to the headers we are sending for request.
I’ve attached my latest code. You’ll need to rejig the #defines and output functions (SysOutputf and others) to fit your project.
However - AWS will typically send you information in the response body when their code rejects your request (mostly commonly because authentication is broken in the header setup code).
What platform are you trying on? iOS has some minor mods needed to the http request object. It might also be that my http code is missing support for redirection because I’m assuming that Epic’s code is magically handling it for me…
Also - did I mention using the open source AWS C++ library now available? If I were starting from scratch I’d be doing this, the time invested would be worth it in the long term.
@ Did that help?
Hi were you able to download and use textures, models and text ? I’m looking for implementing same
@Fieol these days I download textures in normal file format (jpg/png) not uassets but when I started I was loading uassets and they worked.
I seems like people are mounting umaps and related assets from dlc. There are three hurdles you’ll have to master, building the content pack, downloading the content pack and mounting it so that the conent is discoverable.
Good luck!