" Crafty "patching system for Unity projects.

Do you want all 100mb? or only a file?

 

Small update was made to Crafty fixing issues with the FileVersion.

Another update for Mac is schedule to be release later today.

 

Hi,

Where are these updates being released? I checked the Asset Store, and it is still the 1.3.2 version from October last year.

I also have issues with Mac updater using Unity 4.6.1. The patch seems to be applied at first, but if you open the app again, the popup for a new update would appear and ask you to re-update again like nothing happened. I have definitely got the version numbers matched up, and I definitely waited until it said "The patch was successfully created" before I returned to the main Crafty page during the patch creation process.

 

Hello eiffeloberon,

On the first post of this forum it is explained that BETA versions of Crafty can be found on our website, HERE you need to create an account and connect your Invoice.NO that you receive after buying Crafty from the Asset Store. After that you will have full access to all the Crafty BETA versions we are releasing.

Programmer is currently adding finishing touches to Crafty Mac that should repair all the errors. Because Crafty is connected to Unity directly each versions needs to be adjusted separately making the repair process that much longer. ( Crafty is MULTI platform program. ).

 

All Updater errors on Mac OS are almost fixed. Now Updater on Mac will use Mono. It isn't required to be installed, because it's bundled to Updater. Also java on Linux won't be required if we use Mono in Updater on Linux. The only cost is additional 25MB in Updater. Updater for Windows will will remain the same.

 

Hi,

How does this affect games that have previously used an older version of the updater? Would we have to release a completely new build with the new updater to start over, or can we simply update from games that were using a previous version of the updater?

 

eiffeloberon,
New Updater won't affect updating process. Generally only changes in patching methods can be uncomfortable. Due to this we don't recommend to use new binary method in production. We need to implement functionality to adapt new paching method to old Crafty versions.

 

Hey guys, is there any ETA on the Unity 5 RC1 fix?

 

Crafty support for Unity 5.0 will be released within the next few days.

 

Thanks so much

 

Hi, I've noticed in both the current beta and in the stable version the patch remaining size often goes into a negative amount while downloading. Is this something I'm doing wrong or is it a known bug?

 

It's the first time i hear about this, you mean that the number showcasing how much there is left to download goes BELOW Zero ? ( For example minus 10 ? ) If so can you send me more details about this on our support email support@hexte.ch with information on what Unity version you are using on what system and your patch creation process just in case to make sure.

 

Sorry, but has there been a fix for Mac OSX released for beta?

I'm not really trying to get you guys hurried up or anything, but don't give us hope of it being released any time soon if it actually isn't anywhere closed to being finished.

 

Our programmer Wasikuss decided to add a fix for Unity 5.0 to allow all users to use new Updater in Unity 4 and Unity 5 at the same time. It is not a big change and new updater and Unity 5.0 should be released today.

( because we do not own any Mac machines, we have to depend on testers. Unfortunately sometimes we have to wait few days for the proper report. Like for example now ).

 

Is it possible to roll back to a specific version with the updater?
Or select a version to update to? For example having a release set of builds and a builds for testers to use.

 

Tyen,
Yes it is possible. Updater only applies the patches. If you change version manually ( setCurrentVersion ) before checking for updates, then magic will happen. For example

Then if you call setCurrentVersion( "1.2a" ), it will allow to downgrade to 1.1a ( `a` suffix prevents Crafty from download update 1.1 -> 1.2 ). But I think that making more upgrades/downgrades can make mess in versions.txt. To achieve easy way to changing versions, I can unlock method allowing to set target version manually. Then you should handle updates on demand - LaunchieLogic.cs and LaunchieGUI.cs needs to be rewritten. I saved this to our to-do list. In near future we will release demo project showing how to up/downgrade project to any version.

 

Crafy for Unity 1.4.0 b3 has been released!

Change log:
- completely rewritten updater for Mac OS X
- fixed support for Unity 5.0
- BUG: found bug in Updater for Windows causing crash when game is located on other drive than system drive

Tested on 2 projects ( one was sent to us via email ). Patches created on Windows 7 x64 using Unity 5.0.0b18. Tests have been runned on Mac OS X 10.9.4 Mavericks.

Also we have good news for Mac OS X users: before releasing stable Crafty to Assets Store, Crafty on Mac OS X will receive support for binary patches.


//edit: when making patch for platform other than Windows make sure to uncheck checkbox

 

That's awesome. Just what I needed.
Bought

 

Checking in to see status. If developing on Mac Unity 4.6, is it finally working 100% for Win/Mac/Lin updating?

 

Besides one bug that programmer found. ( BUG: found bug in Updater for Windows causing crash when game is located on other drive than system drive )

Non of our testers or clients reported of any problems. We still advise to test everything out before releasing your game with it as it is still a beta.

The only thing that we need to do is repair bug found by programmer, add new GUI test scene ( that was added to Unity in 4.6 ) rewrite entire documentation, create Binary Mac patching ( which should be done in few days at it is much more simple after creating new updater from scratch ) and provide new Error Report system to make our programmers life easier for future bug fixes.

 

Hello, I've got a small bug.
Working with Unity RC 1 and Crafty 1.40b3, delighted to finally have crafty back!

Test client finds the patch, then downloads, then asks permission before closing and opening Updater.
Updater then never moves from 0%, never closes, and never opens the updated client.

If I open the client, it HAS updated, and can find and start the next patch, but updater never signals or finishes it's process.
I've tried running as admin, with and without Debug and Force Admin checked, and checking Standalone in Patchie Import Settings. Same behavior every time. Patchie works in every way except closing Updater and re-opening the updated client.

Any help would be greatly appreciated.

 

So the game is being updated, everything works perfectly in the background but Updater dose not update it self with information on process of installation or closing ?

I did few tests and it works for me so it means that there is more in the background than it should.
First we need to fix one bug for the user as he is waiting for some time now and only now we are able to fix it. ( after adding new updater from scratch ) but we will for sure check this out too, as it should not be behaving like this.

Can you provide me with a little bit more information as of What system you are working on ?.
I can check only on Windows as it is the only system i currently have and there is no problems with the updater. ( from my side of course ).

Also if you can please tell me if there are any error_logs.txt, if yes than send them at support@hexte.ch

EDIT:

It is possible that because of the rush our programmer by accident added few lines of code meant for testing which stop Updater from disappearing while installing the patch ( simple pause system to check if everything works correctly ), when he comes back from work he will make sure everything is deleted from testing.

 

Yes, everything works perfectly except the Updater's final function (display progress, close itself, re-open client)
I'm working with Windows 7, but the issue also appears on our Windows 8 machine, both 64 bit.
No error_logs have been created and Unity doesn't spit any errors when building.

Thanks for the help.

 

Hi, thanks for the new patch .

I have been testing this on Windows, and it gives me this "updater cannot run directly" message during the unpacking process.

I am sure the Forced Admin is checked, and the output_log.txt does not say anything related, nor there is any error_logs.

I have tested this on both my system's drive and my other drive, and the results are the same.

If I reopen the application, it stays at the previous version without anything updated.

Oh, and I am using Windows 7 and 4.6.1f Unity, which I think this is meant to support, correct me if I am wrong here.

I will test this on Mac to see if it works, as I can't get it to work on Windows after numerous attempts.

Ciao.

 

Any update on Crafty Standalone? I'm literally just waiting for that now :<

 

yea same

 

Programmer will release new Beta update tomorrow, to Fix the issue reported to us by certain users.

We also moved one step forward and acquired a Mac machine to test Crafty our self as we cannot wait days for testers to check our builds.

Crafty Standalone is near finish but only one programmer works on both Crafty for Unity and Crafty Standalone.
Because of that, release of Crafty Standalone gets more and more delayed as we first need to make sure that all the issues are repaired on Crafty for Unity.

 

New version has been uploaded to our site. Crafty 1.4.0 b4!

Change Log:

• Patchie: Debug is always enabled. Public var from examples has been removed. Functions which accept debug, are ignoring that parameter.
• Patchie: "Use binary method" is now hidden when BuildTarget is set to platform other than Windows.
• Updater ( Windows ): now all three patching methods are supported ( full, packet and binary ) - it prevents crashes of the game in future when binary method will be enabled as default
• Updater ( Windows ) Fix: updater now works correctly ( closes and runs the game when patching is done )
• Updater ( Windows ) Bug: System.NotSupportedException: The given path's format is not supported - probably fixed, waiting for results from developers
• crafty_beta.txt ( config.json tutorial ): has been recovered from unintended deletion

Tested on Windows 7 64bit and Mac OS X 10.9 using Unity 5.0 b18.

 

Hi,

I am still getting a message box that says "updater cannot run directly" after the latest update on Windows.

Does anyone have any idea what that might be?

 

You are getting this error while using Crafty 1.4.0 beta 4 ?
Do you have this error on a clean test project ? ( a test where only Crafty is in the project, using the standard test scene without any modifications ).?

 

Hi,

I had this problem with 1.4.0b3, and also 1.4.0b4. I have tried the test scene in my project (only building with that scene), but it has the same problem.

I then also tried an empty project along with the test scene, and that problem disappeared.

I guess the difference between the two would be dll's mainly?

- My project uses .Net 2.0 Subset, which has a couple of more dll's in the Managed folder.
- I have two .dll plugins in a Plugins folder
- Some json/xml files in StreamingAssets, some .bin files we created ourselves.

Are there file types that Crafty doesn't quite like?

 

It is possible. We will need to adjust Crafty to files that you use, that may effect Crafty. I don't know exactly what yet may effect Crafty thought, but we will do our best to find them and adjust.

Please contact us at support@hexte.ch i will make sure that Wasikuss our main programmer contacts you tomorrow so that we may adjust Crafty for your and any kind of future projects.

 

Okay, I have managed to fix my problem with "updater cannot run directly" on Windows. Apparently it was simply caused by a space in the Product Name under PlayerSettings.

Hopefully this is gonna help anyone who has the same problem in the future.

And thanks to the quick responses guys, much appreciated.

So it seems like the patch works perfectly for me on both Windows and Mac now .

 

Happy to hear that, we are always happy to help.

Just in case we will add this small note to our documentation for future references.
Also thank you for reporting the fix.

 

Hello,
Just to say that I'm getting a bug with the current stable release of Crafty (v1.3.2).
When I add a dll in the Assets/Plugins folder, Crafty updater is unable to create it by applying the patch.

The error in the crafty_log is as followed:

I tried the latest Beta downloaded from the site (v1.4.0 b4), and the Plugin creation bug is no longer here.

On the bad hand, I experienced the "updater cannot run directly" on Windows, as eiffeloberon describe it:

I can confirm that there is indeed a bug caused by spaces in the Product Name under PlayerSettings. The fix provided by eiffeloberon (remove spaces from the Product Name) seems to work, and the patch is applied correctly .

The stable version worked fine until this plugin creation bug (8 updates during 2 months), so I'm still happy about it. I'm just waiting to see if I will continue with the stable Crafty or the unstable Beta Crafty.

 

We give access to BETA Crafty specifically for such occasions. Crafty 1.4.0 is open for every client beta version of next release, which we use to repair all the errors from 1.3.2 ( previous version ) and adding a lot of function for testing.

There is a big difference between 1.4.0 and 1.3.2:

- New Binary patching for Windows ( and soon Mac ).
- New Updater for all three systems. Mac Windows and Linux.
- Access to Dropbox servers ( you can use virtual storage as your server for patches for now only on Windows )
- Access to Google Drive servers ( you can use virtual storage as your server for patches for now only on Windows )
- Improve API support
- Improve error_logs
- Fixed over 30 bugs and errors.
- Adjustment to Unity 4.6
- Adjustment to Unity 5.0

We will soon add adjustment for new GUI, new online documentation which will be better than simple PDF and much more improve Error Reports system which we will use for all the products we will release. After that if there will be no more errors we will release 1.4.0 ( which we will most likely name 1.5.0 because of the amount of features added ) to the Asset Store.
At the begging we were sending Crafty individually to each person with fixes, but now there is over 50 games/project that use Crafty and over 400 developers, sending Crafty to each user would be a massive waste of time, that is why we open Beta Crafty to every user on our website.

Our programmer already fixed this issue, the problem was not really about spacebar it was about length of the name.
It is already fixed and will be added to Beta 5 which will be release soon with new GUI.

 

WOW HOLD YOUR HORSES.
Since when Crafty can do this !? I never knew Crafty can use any other servers than websites and homemade servers for patching your game ! This changes everything !

 

This feature was added few months ago, few developers explained that they don't have money even for a web-server so we did our best to help.

At the end we added Dropbox and Google Drive support for Windows to allow developers to use free servers. We need to create a good documentation for it ( which i'm working on right now ) plus programmer needs to add support for Mac for this feature.

 

@Thinker
Thanks for your answer. I will keep an eye on the thread to see when the new version come out.

Here is my project, in case you have a list for Crafty's users:
http://godisacube.com

 

Hi,

My project can really wait no longer, along with another project who also uses it (client issues). So I am planning to deploy this with the current Beta patching tool.

Are there any caveats I have to be aware of? Let's say if there's a new stable version of Crafty released in the next month or so, I assume I can still simply update to the stable version but continue to apply patches without having to redeploy the app all over again, because the update method hasn't been changed?

Thanks

 

Hello eiffeloberon, only on very rare occasions we require users to patch entire project from scratch ( which we did only once since the release ), it would ruin the point of an updater if you could not update it by a simple patch.

Non the less, i will ask in the morning our programmer about this, just to be absolutely sure. ( i cannot do it today as there are holidays ).

 

Just a quick update. eiffeloberon i called our programmer today and just to be sure he made few tests with Crafty and newly added system ( self updating ). Overall our programmer is confident that we will never have to ask anyone to download entire project ever again.

New system allows Crafty to update it self the moment it will located game patch created by the new Crafty versions.
You do NOT have to create special patches, this system will know by it self that it needs to update IT self using the game patch.

NOTE: This system is added to our BETA Crafty not 1.3.2 ( it's available on our website Penkura.com )

 

Hi Thinker,

Thanks for following that up .

 

Hey Penkura guys,

I just updated from 1.3.2 to the 1.4.0b4 beta, but sadly I can't get even the simplest kind of patch to work.

So I make two builds with a minimal difference (just the color on the title screen), I make the patch and a config.json, upload the patch to our server, but the game fails to find the patch.

Launchie does initialize, but the log seems to say it can't find the libc library:

This is from Unity's output_log.txt:

Code (csharp):

1.  
2. lgui state is 0
3. UnityEngine.Debug:Internal_Log(Int32, String, Object)
4. UnityEngine.Debug:Log(Object)
5. UnityEngine.MonoBehaviour:print(Object) (at C:\BuildAgent\work\d63dfc6385190b60\artifacts\StandalonePlayerGenerated\UnityEngineMonoBehaviour.cs:108)
6. MyLaunchieGUI:Start() (at C:\Users\...\MyLaunchieGUI.cs:38)
7.  
8. (Filename: C Line: 0)
9.  
10. Launchie: Please wait a while.      <-- that's a print I added to LaunchieGUI.setText()
11.  
12. (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
13.  
14. Fallback handler could not load library C:/myproject/myproject_Data/Mono/libc
15. Fallback handler could not load library C:/myproject/myproject_Data/Mono/.\libc
16. Fallback handler could not load library C:/myproject/myproject_Data/Mono/libc
17. Fallback handler could not load library C:/myproject/myproject_Data/Mono/libc
18. Fallback handler could not load library C:/myproject/myproject_Data/Mono/.\libc
19. Fallback handler could not load library C:/myproject/myproject_Data/Mono/libc
20. Launchie: Game is up to date :)   <---- from LaunchieLogic, believing there is no patch
21.  
22. (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)
23.  
24. lgui state is now 2
25. UnityEngine.Debug:Internal_Log(Int32, String, Object)
26. UnityEngine.Debug:Log(Object)
27. UnityEngine.MonoBehaviour:print(Object) (at C:\BuildAgent\work\d63dfc6385190b60\artifacts\StandalonePlayerGenerated\UnityEngineMonoBehaviour.cs:108)
28. MyLaunchieGUI:Update() (at C:\myproject\Scripts\MyLaunchieGUI.cs:48)
29.  
30. (Filename: C Line: 0)

​

Any clue? All of our launcher gui and the launchie settings are the same as before, and I triple checked version names and the server url... This is on Windows 8 with an x86 build.

Thanks for your help!

 

Januxx,
Everything is ok. libc stands for GNU C library that is used widely in *nix systems. We using it to detect Mac OSX platform. On non-*nix system the error is showing up. We will fix this tonight

 

Alright, thanks for the reply! But I still have the problem that Crafty thinks that the game is up to date when there is a patch available. I'll just keep trying then, I'll update you if I still can't get it working today.

Edit: Or did you mean that this error is the cause of it not finding the patch, but you were already aware of it? That would be great. Appreciate your work either way!

 

Oh sorry, I was in my way to work and I didn't read your post at all. Is there versions.txt next to config.json on server? I yes you should remove it. Launchie use versions.txt over config.json.

 

No, I had already removed versions.txt. Trying to visit the versions.txt url (it's hosted on Amazon S3) gives me a 403: Forbidden response. Maybe Crafty doesn't check for that response code and tries to parse that response's error message as if it was a present versions.txt?

But your response did help me out. I hadn't realized that versions.txt was still supported. I re-uploaded versions.txt with my new version numbers and that worked flawlessly.
So at least my issue is solved for now. Hope this is helpful for you as a bug report

 

Yes, versions.txt and config.json are both supported. We will perform additional tests for versions.txt and config.json.

 

I found 2 bugs in config.json feature. Fix will be released in in a few hours. Then config.json will work as it should.