Skip to content

Slicers GUI Installation

ZeroGravitas edited this page Jun 29, 2021 · 42 revisions

Slicers GUI's Installation of Terror.

Downloading and installing the Slicers GUI tool is a bit scary an experience, because in this computer security-conscious world we live in it means watching a few intimidating security warning screens popping up which we can't evade because the only way to avoid them is paying: the security certificates Microsoft and others provide to validate apps as coming from a known developer are just too expensive for us.

So, we'll walk through the process to show what comes up in that regard.

As with the rest of our tools, the Slicers GUI is available at this repository in our GitHub:

Inside it, we see the usual repository page containing the tool's source code and a description. Instead of downloading that code, we need to use the link in the description, that leads to an installer file hosted by Google Drive (it's too big to be hosted by GitHub, so…):

To download that installer file, we right-click on it and a menu will appear with a download option:

First scare: Google warns us that the file is too big for them to do an antivirus pass. We proceed anyway.

The download of this tool's latest versions weights around 450 MB (Slicers GUI is an Electron-type app, the likes of the popular Discord. Those contain whole internet browsers inside to facilitate web-style programming, which makes them rather big. Add to that that the tool provides now with background music!). Once done, there we have our installer (obviously, the version number will vary with each new release):

We double-click on it aaaaand…

Okay, that feels a little ominous, and leaves us apparently stuck, with no options to go on. Well, they are hidden under that link. If we click on it…

…We'll get a means to go on with the installation anyway:

Now we'll see a fancy animation for a few seconds (the installer takes a little while) and then an initial setup screen appears. Before filling it in, we need to consider a few things.

Setting up.

SWTOR stores its assets in an "Assets" folder that contains a series of rather big .tor files with fairly descriptive names. Sadly, we have no means to easily and quickly find and extract individual files from inside a .tor file. The only practical way to work is to select the ones that are relevant to what we want to do (assemble a player character, assemble a location of the game, extract the game music and sound effects, etc.), extract everything from them, and keep the results around.

And that's the issue: the results, depending on what we want, could fill up from 20 to 80 GigaBytes of storage space! That can be a lot, especially in this era of affordable laptops that top out at 256 GB. If we are very constrained, we might have to consider using external storage (a big USB thumbdrive or a small external HD, etc.)

So, knowing that, let's see what the installer is asking us for (it shows tooltips if we hover over the labels and fields, by the way):

  • Resources Folder:

    The very first thing it's asking us is a location where to place the app's own files: preferences of several types (in human-readable format, by the way), the all-important hashes_filename.text (the file containing the list of known, identified game assets, that we typically update as the game does), etc.

    WARNING: the installer won't create a folder where to put its stuff, so we better do it ourselves. Say, one named "Slicers GUI" 😛 .

    We can put it wherever we want. For example, on the Desktop, but we won't be able to change it without uninstalling (through Windows' Preferences Panel's apps options) and reinstalling.

  • Assets Folder:

    The second thing it asks us is the location of SWTOR's "Assets" folder. If we used swtor.com's installer to install the game, it typically is at:

    C:\Program Files (x86)\Electronic Arts\BioWare\Star Wars - The Old Republic\Assets

    If we installed the game through Steam, the default location is:

    C:\Program Files (86)\Steam\steamapps\common\Star Wars – The Old Republic\Assets

    This setting can be changed afterwards (for example, to point at the assets of a SWTOR's Public Test Server download).

  • Output Folder:

    Finally, it asks us where the result of our extracting and converting activities (those big assets extractions, sound and 3D file conversions, etc.) will be placed. As explained, the worst case scenario (extracting just everything) means around 80 GBs, and then we might want to have some spare space for additional stuff.

    This setting can be changed afterwards, so that the results of the extraction can be moved around if needed.

    WARNING: don't select the same folder used to hold the app's own files. The reason is that, so far, the only way we have to update the app is by uninstalling an old version and installing a new one, and the process deletes that folder. If we put everything in there, an update would mean losing the extracted assets and we would have to extract them again.

After we have selected the locations for everything, the installer will put what it needs in the app folder we selected, and place an app shortcut on the desktop. And that's it! On finishing, the installer will launch the app for us.

As we can see, it's an all-in-one kind of affair, with a few features already working and others pending implementation. It shows the setup directories that we are allowed to change, as aforementioned, plus another that is meant to point to game character folders exported by TORCommunity.com's Character Designer or by its database's 3D viewer.


INTRODUCTION

IMPORTING SWTOR MODELS INTO BLENDER: A BRIEF OVERVIEW.
Check this intro first. Afterwards, you can jump directly to the guides on extracting PCs, NPCs and others.


TOOLS

Downloadable Tools (All Links Page):

Online Tools:

No longer working:

  • EasyMYP Windows app.
  • Noesis Windows app.

THE COMPLETE GUIDE TO AUTO-EXTRACTING AND ASSEMBLING PLAYER CHARACTERS AND NPCs:

READ THE BROAD STROKES FIRST: YOU'LL SEE IT'S EASIER THAN YOU THINK!


ASSEMBLING GAME LOCATIONS AUTOMATICALLY:


LOCATING AND ASSEMBLING ASSETS MANUALLY:


OTHER GUIDES (WIP):


MODDING

Modding isn't working since SWTOR moved to 64-bit codebase. Unless a new coder takes charge, it'll stay so indefinitely.


DATAMINING

Basically, use Jedipedia.net's tools and check our Discord. We'll see about adding new material, but this is very involved stuff.


SWTOR TECHNICAL INFORMATION:


OTHER RESOURCES:

Clone this wiki locally