Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Creat

#16
OK good. At least we know there isn't related to some file corruption (or even infection) on my end.
#17
(All checksums are SHA256)

I get a different checksum, and always the same no matter where/how I generate it (upload the file to a checksum generator, generate it on my main machine or on my small linux server):
3bf6ea627c3dee69fbced6cedf8bc6862d57939852a8e235b9488bff15e05338  AtomicTorch.SpaceRPG.Server.RuntimeMono.exe

For comparison, here is the checksum of the downloaded archive (it is the same for the one downloaded by the launcher and the one downloaded manually from the website):
67668bc67a75b4184c766f3ce30c98c65c73e25f83254d3a84a6f4bbe36aa6ff  VoidExpanse_v0.9.9_Win.zip

Could someone else please crosscheck as well? This tool (https://github.com/jessek/hashdeep/releases/tag/release-4.4) can generate the checksum on windows (via sha256deep or sha256deep64 for 64bit versions of windows).

Edit: to clarify, I have also redownloaded the archive for creating the checksum on the linux machine, to make sure it didn't pass through my main PC even just in ZIP form.
#18
I think it was 'caught' by the heuristic, which includes behavior. Meaning the act of downloading, extracting, etc. might well play a role. It could also be the unusual file extension (if it's a normal executable and not a consequence of being bytecode or something) or any combination of those things.

I just tried again by just manually extracting the downloaded archive (of 0.9.9, downloaded by the launcher), and it still stopped on the file: AtomicTorch.SpaceRPG.Server.RuntimeMono.exe with Win32:Evo-gen [Susp]
I have also uploaded it to VirusTotal.com, where it came back clean for every scanner as well (including avast).

Could you, just to make sure it's not on my end, tell me the MD5 of the file so I can double-check that it's in fact the exact same as it is on your end?
I only very rarely get any virus alerts at all (and all of them verified false positives). I'd say about one in six moths or so, hence my heightened concern.

As for scanning only with MS Security Essentials, please note that they don't have the best track record (Source 1 (http://www.av-test.org/en/home/), Source 2 (https://www.virusbtn.com/vb100/latest_comparative/index)). If I was releasing software, I'd probably scan it with at least a few AV products. As a last note, I'm aware that avast is kinda known for it's false positives (http://chart.av-comparatives.org/chart1.php) (at the link, select 'false alarm test' in the drop down), but it would still be nice if this could be solved once and for all :)
#19
Hello,

I wanted to update VoidExpanse today and (once again) the launcher failed to do so. First I was told the 8.4c couldn't be updated (which is fine). It then downloaded the full install, but failes at installing when it gets blocked by my AV (avast). It detects 'Win32:Evo-gen [Susp]' in '50h3pcw4.xmz', located in the folder: ...\AppData\Local\Temp\AtomicTorchLauncher\VoidExpanse_Win_v0.9.9.zip.extract\VoidExpanse_v0.9.9_Win\Server_Mono

Since this file is pulled out from under the launcher, he's understandably upset it's no longer there even though he's just extracted it ;)

I remember there were some troubles with false positives in the past, can I assume this is another one?
What AV-suites do you use on your end to check archives are clean?

Thanks
Creat
#20
Ok that sounds pretty good then, looking forward to trying it :)
#21
Hello again, I know I'm a bit late to the part, but I'll add my 2 cents anyway ;)

From looking at the graphs you posted it doesn't seem like there are skill requirements for the basic weapon types. I'd kinda like it if we only started with a single light type, i.e. beam/pusle. Kinetic and Missiles should require a skill. Or am I just misinterpreting the tree there?
#22
Thanks, I can confirm that it all works fine now!
#23
Ah, after a bit of checking I think I've found the issue. You're using atom-formatted links, but you specify in the header that it's an RSS 2.0 (http://en.wikipedia.org/wiki/RSS) feed. While similar, those are not the same. The fix is rather trivial: most of the feed is actually perfectly well formatted as RSS 2.0, with the exception of the links.

So just change <link href="https://atomictorch.com/Post/Id1064"/> to this <link>https://atomictorch.com/Post/Id1064</link>

Side note: The reason I get every article linked to the main page is that the channel link is the only one that's formatted properly, so it falls back to it for the articles.
#24
Game discussion / RSS feed for the development blog
July 07, 2014, 11:41:30 AM
Hello again!

I have recently added the RSS feed for the blog to my feed reader and noticed that the articles aren't properly linked. All articles simply link to atomictorch.com (http://atomictorch.com) instead of atomictorch.com/Post/Id1065 (http://atomictorch.com/Post/Id1065) (as an example). Having a direct linkk would be especially nice when reading on my phone, where navigation is a bit cumbersome...
#25
Game discussion / Re: ships and "classes"
June 23, 2014, 08:57:04 PM
Dunno about what ships are planned, but as far as I know the class selection has little impact at the moment: It doesn't change the skill tree (yet), as I understand it. Different classes will have somewhat different skill costs for different things, maybe even exclusive parts. Currently though, it only changes your starting items, i.e. the extra thing you have in your cargo hold after character creation (I imagine just to be able to test weather selecting a class basically works).

Please correct me if I'm wrong, or if anything was changed about this recently and I missed it somehow...
#26
Bug reports / Re: Launcher shenanigans
June 18, 2014, 02:37:38 PM
Aaaaand it's completely stuck this time: Launcher tells me there's a new version (0.8.4c, installed is 0.8.3). I click update and it downloads a patch (of about 50 MB). It tries to patch for a while, but fails (Invalid checksum after decoding window). I can only click repair, which quickly finishes and he's satisfied that my 0.8.3 is fine again. Now I can again click either play or update (as in the beginning), update doesn't re-download of course, but this loops on forever. Log is attached!

Edit: I've just deleted the installed version to get a fresh start this time, maybe it won't break this time around ;)


18.6.14 22:58:08.3069: Important:
Log file opened

18.6.14 22:58:09.3919: Important:
AtomicTorchGameLauncher v0.7.1b started. Current data directory: C:\Users\Creat\AppData\Local\AtomicTorchStudio\Launcher\

18.6.14 22:58:11.5130: Important:
Re-checking of "VoidExpanse" v0.8.3 is required

18.6.14 22:58:11.5590: Important:
Sync apps view models: 1

18.6.14 22:58:11.8331: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 22:58:12.2291: Info:
Applications list updated from server: 1 total items

18.6.14 22:58:12.2321: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 22:58:12.2341: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 22:58:12.2591: Important:
Sync apps view models: 1

18.6.14 22:58:12.2691: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 22:58:33.4133: Important:
App "VoidExpanse" v0.8.3 status changed: Installed

18.6.14 22:58:33.4543: Important:
IsRecheckingRequired set to False

18.6.14 22:58:38.7056: Important:
App "VoidExpanse" v0.8.3 status changed: Downloading

18.6.14 22:58:38.7456: Important:
Added download task: Title: Patch VoidExpanse from v0.8.3 to v0.8.4c, DownloadFilePath: C:\Users\Creat\AppData\Local\AtomicTorchStudio\Launcher\Downloads\Patch_VoidExpanse_Win_v0.8.3_to_VoidExpanse_Win_v0.8.4c.zip, Url: http://atomictorch.com/ClientService/FilePatchDownload?masterToken=7c6e7479-b5a2-4f9f-a83c-6cd080f35a38&itemKey=20vyW0GXx4Ss!*X.yu9%7BGG%5D7(u5aRfWQyQ%3B%2BF%23%24EYI!pOWe%25)E8P%25rRt9n%7BqW61%5E&isExperimental=False&platformKey=Win&fromVersion=0.8.3

18.6.14 22:58:38.7516: Important:
Started download task: Title: Patch VoidExpanse from v0.8.3 to v0.8.4c, DownloadFilePath: C:\Users\Creat\AppData\Local\AtomicTorchStudio\Launcher\Downloads\Patch_VoidExpanse_Win_v0.8.3_to_VoidExpanse_Win_v0.8.4c.zip, Url: http://atomictorch.com/ClientService/FilePatchDownload?masterToken=7c6e7479-b5a2-4f9f-a83c-6cd080f35a38&itemKey=20vyW0GXx4Ss!*X.yu9%7BGG%5D7(u5aRfWQyQ%3B%2BF%23%24EYI!pOWe%25)E8P%25rRt9n%7BqW61%5E&isExperimental=False&platformKey=Win&fromVersion=0.8.3

18.6.14 23:00:56.0565: Info:
Downloaded successfully: Title: Patch VoidExpanse from v0.8.3 to v0.8.4c, DownloadFilePath: C:\Users\Creat\AppData\Local\AtomicTorchStudio\Launcher\Downloads\Patch_VoidExpanse_Win_v0.8.3_to_VoidExpanse_Win_v0.8.4c.zip, Url: http://atomictorch.com/ClientService/FilePatchDownload?masterToken=7c6e7479-b5a2-4f9f-a83c-6cd080f35a38&itemKey=20vyW0GXx4Ss!*X.yu9%7BGG%5D7(u5aRfWQyQ%3B%2BF%23%24EYI!pOWe%25)E8P%25rRt9n%7BqW61%5E&isExperimental=False&platformKey=Win&fromVersion=0.8.3

18.6.14 23:00:56.0675: Info:
File downloaded for update: DownloadFilePath: C:\Users\Creat\AppData\Local\AtomicTorchStudio\Launcher\Downloads\Patch_VoidExpanse_Win_v0.8.3_to_VoidExpanse_Win_v0.8.4c.zip, DownloadUrl: http://atomictorch.com/ClientService/FilePatchDownload?masterToken=7c6e7479-b5a2-4f9f-a83c-6cd080f35a38&itemKey=20vyW0GXx4Ss!*X.yu9%7BGG%5D7(u5aRfWQyQ%3B%2BF%23%24EYI!pOWe%25)E8P%25rRt9n%7BqW61%5E&isExperimental=False&platformKey=Win&fromVersion=0.8.3, Status: Success

18.6.14 23:00:56.0735: Important:
App "VoidExpanse" v0.8.3 status changed: Patching

18.6.14 23:01:22.0409: Error:
File patching error

Exception AtomicTorch.Launcher.Core.Helpers.Vcdiff.VcdiffFormatException: Invalid checksum after decoding window
   -------------------------stack-------------------------
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.qo2jkP16uG()
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.dEqjHvcheu()
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.rYYjKKfU53(Stream  , Stream  , Stream  )
   at Ix2WVNjeNuwYynavWq0.vBvIr3jb0P28HEwfRDD.D6upfd8a2G(String  , String  , String  )
   at Ix2WVNjeNuwYynavWq0.vBvIr3jb0P28HEwfRDD.vvopqFTkQV(String  , String  , String  , Action`1 progressChanged)

18.6.14 23:01:22.1009: Important:
Button BtnOk focused

18.6.14 23:30:33.5551: Error:
Can't apply patch: "VoidExpanse" v0.8.3

18.6.14 23:30:33.5581: Important:
App "VoidExpanse" v0.8.3 status changed: Corrupt

18.6.14 23:30:34.5942: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 23:30:36.2863: Important:
App "VoidExpanse" v0.8.3 status changed: Installed

18.6.14 23:30:45.0978: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 23:30:46.7949: Important:
App "VoidExpanse" v0.8.3 status changed: Installed

18.6.14 23:30:46.8089: Important:
IsRecheckingRequired set to False

18.6.14 23:30:46.8359: Important:
Button BtnOk focused

18.6.14 23:30:50.4781: Important:
App "VoidExpanse" v0.8.3 status changed: Patching

18.6.14 23:31:01.0737: Important:
Sync apps view models: 1

18.6.14 23:31:01.0817: Important:
App "VoidExpanse" v0.8.3 status changed: Patching

18.6.14 23:31:02.3938: Info:
Applications list updated from server: 1 total items

18.6.14 23:31:02.4108: Important:
Sync apps view models: 1

18.6.14 23:31:02.4148: Important:
App "VoidExpanse" v0.8.3 status changed: Patching

18.6.14 23:31:03.5748: Error:
File patching error

Exception AtomicTorch.Launcher.Core.Helpers.Vcdiff.VcdiffFormatException: Invalid checksum after decoding window
   -------------------------stack-------------------------
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.qo2jkP16uG()
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.dEqjHvcheu()
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.rYYjKKfU53(Stream  , Stream  , Stream  )
   at Ix2WVNjeNuwYynavWq0.vBvIr3jb0P28HEwfRDD.D6upfd8a2G(String  , String  , String  )
   at Ix2WVNjeNuwYynavWq0.vBvIr3jb0P28HEwfRDD.vvopqFTkQV(String  , String  , String  , Action`1 progressChanged)

18.6.14 23:31:03.5858: Important:
Button BtnOk focused

18.6.14 23:31:05.9380: Error:
Can't apply patch: "VoidExpanse" v0.8.3

18.6.14 23:31:05.9420: Important:
App "VoidExpanse" v0.8.3 status changed: Corrupt

18.6.14 23:31:07.5221: Important:
App "VoidExpanse" v0.8.3 status changed: Checking

18.6.14 23:31:09.2112: Important:
App "VoidExpanse" v0.8.3 status changed: Installed

18.6.14 23:31:13.1784: Important:
App "VoidExpanse" v0.8.3 status changed: Patching

18.6.14 23:31:23.5400: Error:
File patching error

Exception AtomicTorch.Launcher.Core.Helpers.Vcdiff.VcdiffFormatException: Invalid checksum after decoding window
   -------------------------stack-------------------------
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.qo2jkP16uG()
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.dEqjHvcheu()
   at H8sSufj9y98N4GhQVRy.PZwHcZjRXS71JGEDcRx.rYYjKKfU53(Stream  , Stream  , Stream  )
   at Ix2WVNjeNuwYynavWq0.vBvIr3jb0P28HEwfRDD.D6upfd8a2G(String  , String  , String  )
   at Ix2WVNjeNuwYynavWq0.vBvIr3jb0P28HEwfRDD.vvopqFTkQV(String  , String  , String  , Action`1 progressChanged)

18.6.14 23:31:23.5530: Important:
Button BtnOk focused

18.6.14 23:31:56.0628: Error:
Can't apply patch: "VoidExpanse" v0.8.3

18.6.14 23:31:56.0668: Important:
App "VoidExpanse" v0.8.3 status changed: Corrupt

18.6.14 23:34:29.3906: Important:
Log file closed
#27
Ideas and suggestions / Re: Some suggestions
June 12, 2014, 05:08:58 PM
Quote from: kyokei on June 09, 2014, 12:07:20 PM- Borderless window mode

That is actually already possible. Since this is a unity-engine game, all you have to do is add "-popupwindow" to the command line (not the quotes obviously). This switches the normal windowed mode to a borderless one (it has no effect if you're running the game in fullscreen).

If you are using the launcher, you can put this into a special file where the command options are then read from. Create a file called ".launch_args_custom" as a text file next to VoidExpanse.exe and only put "-popupwindow" in there. Note to save it without extension (or save as .txt and then remove that extension).
#28
Bug reports / Re: Launcher shenanigans
June 10, 2014, 04:42:27 AM
Yea I understand it's not a huge problem at the moment, and that it's still early in development and certainly not a big deal at this point (even having a launcher already is quite luxurious and makes updating much easier for everyone, even when it's just in appdata). I just hope that it eventually will move to program files, or at least support it. I also didn't mean to write that much text, it was just there after a while :o

My chrome is installed in Program Files, according to that superuser-link that is also the default and it will only fall back to appdata if the user says 'no' to UAC, when he doesn't even have the option of saying yes (no admin account) or it's installing an update and was already installed there. They kinda have to use every opportunity to get installed to grab that marketshare though ;)

In the long run I hope program files (or any other place, but installed and using appdata for storage) will be the default, or at least an option. Allowing to be run from a single folder (without installing) could still be quite easily allowed by checking for a .noinstall file or any number of similar measures (like simply running locally when the "Save" and "Mods" folders are there, checking if the privileges work and just asking for UAC elevation if necessary). The unity log will be automatically redirected to the virtual store btw., that's what it's there for (and that's probably fine for a log file).

But as I said, just wanted to bring this to your attention. It's anything but a pressing issue, I'm happy with the fact that you know about it. All I wanted to achieve here  ;D
Same with the launcher popups btw, seriously not a problem and (probably) even only occurs when there's a launcher update AND the install is corrupt...
#29
Bug reports / Re: Launcher shenanigans
June 10, 2014, 02:09:10 AM
Quote from: ai_enabled on June 10, 2014, 01:58:52 AM
Thank you for report!
Our quality control is somewhat "indie" :-)... the issue was just a small mistake in code, not a hang/freeze.
The issue was fixed, new release 0.7.1b published.
What about launcher auto-update? How this feature works for you? Is there any issues with it?

Basically yes, but there seem to be some thing going on at the same time. When I started the launcher just now, it popped up the progress dialog showing the new version download (as there is a new launcher, obviously). Then I get a popup, covering this dialog, telling me the installation is corrupt (and I should repair). Then that get's covered with a dialog that says it's done updating and needs to restart (I think?), but it restarts without problems to the new version.

Maybe just don't start checking the installation until the launcher has checked for a new self-update, and all is well?
#30
Bug reports / Re: Launcher shenanigans
June 10, 2014, 02:02:47 AM
Quote from: ai_enabled on June 10, 2014, 12:08:50 AMAbout UAC elevated rights - if I understand you correctly, you want to have all launcher content/game data to be relocated into Program Files directory. But then it will require administrative rights to run the GameLauncher application - otherwise it just can't modify data files now stored at Program Files directory, and games also can't be launched without elevated rights (they're also would like to write something nearby). So that's why we decided to store everything in %appdata% directory. It will not ask for any administrative rights and users can store launcher data somewhere in convenient location like "D:\Games". If you know how to improve it, please share you thoughts. Thanks!

Glad you asked ;) I originally intended to start a new thread about this, but might as well just continue the flow here. Having executable files in AppData is at the very least bad practice and at worst even dangerous (to a degree). The only software I know that has it's .exe in appdata is Spotify, and I really hate that about them. The only thing it 'saves' is a single UAC request upon installation or update, and it also means that every user has his own copy of Spotify (oh why...).
On windows there are different standard folders to separate executables and static data (Program Files [x86]) from user-data like save games, configurations/options etc (various types of AppData). If some data should be shared between multiple users (but also be modifiable), there is the ProgramData folder for that purpose.
This represents the MS guidelines for software development on windows [1], and the UAC elevation mechanic was introduced on Win Vista (and prevails ever since) with very good reason and builds upon that. It allows users to execute programs normally with limited privileges, and only elevate to admin status when it's actually needed. This in turn means that users can't (intentionally or not) modify the programs or their fixed data, but it also means that any malicious software can't. Whatever normal program those might use to gain access is only running with normal privileges. This way no virus can infect executables in Program Files to spread itself or persist (or just 'do damage'), because it simply can't write there.

If a program wants to write to Program Files because it has to (like an updater), it can request UAC elevation (prompting the standard dialog for this, like any software installer) and then write to the folders normally. Some basic example code on how to check for admin privileges and request elevation via UAC if it's needed: C++ Version (http://code.msdn.microsoft.com/windowsdesktop/CppUACSelfElevation-5bfc52dd), C# Version (http://code.msdn.microsoft.com/windowsdesktop/CSUACSelfElevation-644673d3)

Sot he patcher and game itself should be in program files, configuration files should go to appdata\roaming and savegames either also to appdata\roaming or a more convenient location like My Documents (or My Documents/My Games). This might also be a good place to place the Mods folder, as every user can find it easily to install them.

I would have the launcher check if it's in the 'right place' via a registry value or configuration file (in appdata) upon launch. If it's not, ask the user if he wants to install it somewhere, suggesting a new folder in 'Program Files (x86)'. If he accepts, request UAC elevation and copy the launcher.exe there. If he doesn't (i.e. he wants to keep the launcher.exe where it is now) just store that path as the installation path and it's also fine.
On later starts the launcher can simply check if there is an update normally like it does now, downloading the .zip files for installation and patching to ProgramData. Once done, ask for elevation, do the actual patching/installing, and drop elevation again. Dropping isn't critical, but ensures the game is not launched with admin privileges without any need.

The changes required for this are actually rather minimal. The suggested small installation routine could be skipped if necessary or too much work (though it should be rather simple). All other changes would basically just exchange a few fixed path entries for queries of the dynamic locations (like appdata, my documents and the like) and that's it. A change like this now is also rather trivial for users to migrate their stuff (which basically means copy a few savegames, if that), especially considering it's still early alpha and things like that are expected.

I really hope you consider this (at least to some extent), and sorry for writing this wall-of-text...

[1] This answer on StackOverflow (http://stackoverflow.com/questions/13163611/where-is-the-guideline-that-says-you-shouldnt-write-to-the-program-files-area) nicely quotes the important parts of the technical requirements, and also links to the full document detailing the MS Guidelines.