Tanto Edge Oct 20, 2013 @ 3:45pm
Publishing locally to appdata folder? Then loading a previous version of the UGC!??!??
I have two machines I use the SRR Editor upon.
An XP and a Win7 machine.
Of those two, the Win7 machine works flawlessly, with locally published UGC appearing in my content and updating without hiccup.

On the XP side of things, the UGC saves to C:\Documents and Settings\username\My Documents\Documents\Shadowrun Returns\ContentPacks

It PUBLISHES to C:\Documents and Settings\username\Local Settings\Application Data\Harebrained Schemes\Shadowrun Returns\ContentPacks

SRR doesn't read from that folder, so I'm forced to move the packs. Boohoo for me, right?

Here's the thing: Why is it that when I publish the UGC, I end up in a previous version of the UGC? How is that possible?

I'm not making that up and I was ripping my hair out trying to solve this friggin mystery.
I'm on v1.0.4 and I playtest my map, and I end up in a previous version.
I deleted all the userdata / temporary data and cleared temporary data, copied the UGC from my other machine, opened it up, published locally, moved the zip to the C:\Steam\SteamApps\common\Shadowrun Returns\Shadowrun_Data\StreamingAssets\ContentPacks folder and walla, I'm in a totally different version then the one I just built and published.

How does that happen?
Last edited by Tanto Edge; Oct 20, 2013 @ 3:45pm
Showing 1-11 of 11 comments
< >
Tanto Edge Oct 20, 2013 @ 6:31pm 
I've uninstalled and reinstalled SRR through Steam and as I imagined, there was no difference.

However, I unsubscribed and deleted the UGC, then transferred the locally published pack, and walla; all is well.

In short, the UGC I'm developing was being overridden by the subscribed version. Once I removed the UGC and unsubscribed, running the Locally Published version from the primary contentpack folder worked.

It's still publishing to the most idiotic location and I can't figure out where to change the destination.

I sincerely wish there were a way to configure paths as such in the editor. Just tell the editor to consider a specific location everytime it goes to publish to...
HBS_Jeffrey  [developer] Oct 21, 2013 @ 4:11pm 
Hi there Tanto,

I would like to try to work with you to provide answers, or figure out exactly what the issues are so that we can get them resolved.

From what I understand you seem to be having conflicting issues with UGC that you are creating, and are also subscribed to. Or you are having issues determining what each state of your UGC is and where they may be located?

When you are creating a UGC and are working on building your UGC there is a project.cpack.txt located under your documents/Shadowrun Returns/ContentPacks/UGC. This is the "working version" of your UGC and can only be played through the Editor via the test button.

When you have Published your content pack locally then creates a UGC.zip located in your AppData/Harebrained Schemes/Shadowrun Returns/ContentPacks. This is what is pushed up to steam when you publish to the steam workshop. This version of your UGC is also recognized by Shadowrun Returns and is playable via the Content menu and under New Game (if applicable to your UGC).

If you have subscribed to a UGC then it will download a UGC.cpz to you Steam/userdata/[STEAMID]/234650/remote/contentpacks. This is the playable verison of the subscribed UGC and can be played via the Content menu or under New Game (if applicable to the UGC). If you are subscribed to your own UGC (that you have created or have the UGC.zip files on yoru computer) the loacally published version (UGC.zip) should be found under New Game instead of the steam subscribed version (UGC.cpz).

I hope this helps clear up your understanding of the content packs and the different states it goes through when you are working, publishing locally, and finally publishing to steam.
Southwind Oct 22, 2013 @ 12:15am 
I found that it's not safe to subscribe to your own published UGC. It ALWAYS causes issues, at least for me (and there's no real reason to). I completely re-published a different version, never subscribed to it, and haven't had any issues with it. I think a good fix on HBS side (maybe Steam), is if they disabled self-subscribing somehow.
Tanto Edge Oct 22, 2013 @ 11:50am 
Hi Jeff, super cool of you to take the time to provide such a response.

Not sure what you do at HB, but thanks to all the team for what they've provided the community. Every new feature is a blessing that is both unexpected and exciting to receive!

First, I'm familiar with the file system. I've been getting really familiar with it as I stumble through the work.

The issue I'm having is like this:
If I subscribe to my UGC on my garage machine, anytime I run the UGC, it runs the subscribed one. I had this occur even through an editor playtest.

Now, when I publish locally, typically I Publish Content Pack To... and select the root contentpacks folder. If I do not do this, the published files end up in the appdata folder, nestled comfortably where the game doesn't care to look.

The subscriptions system works properly otherwise, in that the UGC's are downloaded, into their own numbered folders, and play correctly. Everything is working correctly thereby.
However, if I have subscribed to my UGC, that copy is what is run by the game everytime, regardless of how I try to run my locally published copy.

Literally speaking, I select the locally published version and SRR runs the subscribed version.

The really confusing part is the fact that my main machine can be subscribed and have a locally published copy without issue. I can open and make changes to either without a hiccup. This is on Win7.

The garage machine is on WinXP. If I subscribed to my UGC, that is what is loaded by the engine and the working copy is ignored.
HBS_Jeffrey  [developer] Oct 23, 2013 @ 11:43am 
Tanto,

Can you tell me what directory you are calling the "root contentpacks folder"?

When you publish locally (to the AppData folder) Shadowrun Returns should recognize this location and you should be able to play your UGC. This is also where Shadowrun Returns looks for UGC to push to the Steam Workshop.
Tanto Edge Oct 23, 2013 @ 5:11pm 
The primary game contentpacks folder, where Seattle, Core and DMS are located.

Edit: C:\Steam\SteamApps\common\Shadowrun Returns\Shadowrun_Data\StreamingAssets\ContentPacks

I agree completely, Jeff. It should recognize. I completely concur ;)

As a quick fix that would alleviate a lot of peoples issues, I suggest you let people configure which folder the editor saves to. Wouldn't this help with the whole concept of differing operating systems, etc?
HBS_Jeffrey  [developer] Oct 24, 2013 @ 11:53am 
So the best fix for your problem is to unsubscribe from your own UGC, and just to publish locally to your AppData folder. This should alleviate any issues that you are experiencing with Shadowrun Returns playing the incorrect version of your UGC.

The file structure we have in place allows the game to read the correct version of your local files automatically, however if multiple content packs with the same ID exist, Shadowrun Returns will load the first content pack it finds, reguardless of version. If your computer requires you to publish your content pack elsewhere (if you have a unique file structure), press Publish Content Pack to..., and choose your location. That being said, the automatic publishing system (publishing to AppData) is designed be user friendly as Shadowrun Returns is not able to look through your whole computer for all content packs.
Tanto Edge Oct 24, 2013 @ 8:19pm 
Right, but what I'm doing is publishing to the core folder.

If I publish locally, that is, publish to the appdata folder, the UGC does not show up in Shadowrun.

Not to be a ♥♥♥♥, but you actually just told me to do what I'm already doing.

So in short, I'll assume there is no actual fix for this 'issue'?
Tanto Edge Oct 28, 2013 @ 10:52am 
Okay, well since Jeff is clearly not going to respond to this post, I'll simply follow up with:

No, there is no official solution, this aspect of the engine is broken and under Windows XP this behaviour is typical.

Under Win7 though, all is well.
HBS_Jeffrey  [developer] Oct 28, 2013 @ 11:47am 
Tanto,

I am sorry to hear that you are still having issues with creating your UGC for Shadowrun Returns. Please ensure that you have Unsubscribed from your own UGC (and deleted the downloaded content pack from your Steam folder), removed the Published zip file from Shadowrun Returns core data folders, and only Publish your UGC Locally into your AppData folder. If you follow these instructions then you should have only 2 copies of your UGC on your computer at any time, a published zip file in your AppData folder (before and after publishing your UGC to the Steam Workshop), and a working copy of your UGC in your Documents folder.

I would like to add that Shadowrun Returns must be able to look into your AppData folder, as this is where Shadowrun Returns publishes UGC to the Steam Workshop. If you are still having issues with this I would like to ask you to reach out to customer support at info@hbs-studios.com where we will work with you personally to resolve your issues, or find out what is the problem so we can push out a fix.

Thank you for your patience as we attempt to resolve your issues,
HBS Jeffrey
Tanto Edge Oct 29, 2013 @ 9:03pm 
It would be highly convenient if we could just define a folder where the editor could place the package so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so it would be highly convenient if we could just define a folder where the editor could place the package so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so it would be highly convenient if we could just define a folder where the editor could place the package so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC so when the package is compiled the UGC will simply be placed where the user defines that UGC files should be placed because if we define a folder than the program will simply know where to place the UGC because that's all we really want here, eh?



For those just joining us:

Symptom(s): You are using Windows XP.
You are loading or playtesting a locally published UGC while you are subscribed to your published version. SRR only loads the publically published version.

Cause: You are subscribed to your own content, and using Windows XP.

Solution: You can't be subscribed to and edit a UGC of the same name in Windows XP.
Unsubscribe, then go into your steam/userdata/[STEAMID]/234650/remote/contentpacks and find your now unsubscribed UGC. Delete it.

All is now at peace. Go and be fruitful.

Notes: Does not affect Win7 (Vista?) users.
Showing 1-11 of 11 comments
< >
Per page: 15 30 50
Date Posted: Oct 20, 2013 @ 3:45pm
Posts: 11