Latest build gives errors for every song, Mac!!! Dannazione

@@mrctll, use another build than, I can't fix anything right now, sry :)

but can you describe me the problem, please?

@@mrctll, use another build than, I can't fix anything right now, sry :)

 

but can you describe me the problem, please?

 i send an image of output!! My english is bad https://www.dropbox.com/s/buk9rjb940a6jqs/2014-12-09%2007.43.55%20pm.png?dl=0

@@mrctll, yis, thank you I'll fix it asap

@@mrctll, fixed as I can say ;)

I have the same issue.... che peccato!!! :D 

Now i'm using an old build 621ca588 beta that works with mono framework. But the last three version didn't work with wineskin, a very great wrapper for mac that runs windows apps. The only way for autoupdate, with mono the best way is to re-download the toolkit. The bad thing with winskin is that the wrapper is a little bit.... very big :D :D

 

Spero di aver scritto qualcosa di comprensibile... :D :D

 

Buone festeeeeeeeee... :D

6d3271c341b7 under OSX 10.10 gives this error when trying to generate a new CDLC. Everything should be right according to the tutorial.

 

http://i.imgur.com/0l4jiRX.png

@@Huumetucca, at mac you need ability to run nvdxt.exe so you'll be able to generate dds files. I'm thinking of switching to nvtt libary(core lib of nvdxt) so you could use it without wine and so on. you can wait untill I'll switch to nvtt or switch to PC version of the toolkit(there was one wiveskined version somwhere here).

It's already known issue, sorry :)

The latest build now, works well on mac 10.10. Grazieeeeeee  :D :D :D

@@Huumetucca, at mac you need ability to run nvdxt.exe so you'll be able to generate dds files. I'm thinking of switching to nvtt libary(core lib of nvdxt) so you could use it without wine and so on. you can wait untill I'll switch to nvtt or switch to PC version of the toolkit(there was one wiveskined version somwhere here).

 

It's already known issue, sorry :)

 

Ah, okay, cheers. I guess I just need to reinstall my Windows then.

sorry if this sounds like a broken record but I was using v2.5.0.0 until I saw this today, but every time I extract the files for 2.6.0.0 my AV would always delete it.. should I just restore all those deleted files? or just keep using 2.5.0.0?

sorry if this sounds like a broken record but I was using v2.5.0.0 until I saw this today, but every time I extract the files for 2.6.0.0 my AV would always delete it.. should I just restore all those deleted files? or just keep using 2.5.0.0?

Use the latest Toolkit build from here http://www.rscustom.net/builds/latest_test.zip and if for some reason your AV picks it up, then disable your AV real time protection and add the extracted folder to the AV ignore/exception list. There is nothing dangerous about the newer Toolkit versions. The AV is a false positive and the same thing happens with keygen programs.

 

 

 

 

sorry if this sounds like a broken record but I was using v2.5.0.0 until I saw this today, but every time I extract the files for 2.6.0.0 my AV would always delete it.. should I just restore all those deleted files? or just keep using 2.5.0.0?

Use the latest Toolkit build from here http://www.rscustom.net/builds/latest_test.zip and if for some reason your AV picks it up, then disable your AV real time protection and add the extracted folder to the AV ignore/exception list. There is nothing dangerous about the newer Toolkit versions. The AV is a false positive and the same thing happens with keygen programs.

 

 

 

  cool, thanks

Saw this update today:

"2015-02-10: Implemented basic Techniques support"

 

I have no idea what that means^^

Is there a way to learn what the updates in the Toolkit actually do? :)

(I did find the commit on github, but looking at the code still doesn't give me a clue...)

 

Regards,

Azrael

@@Azrael, if code doesn't help then ask me :)

this update includes generator for techs, you can find it ingame in Learn a song, there menu for tech you won't miss it
For now it supports only 16 basic techs.

Ok, now I get it. You can load up explanations of the techniques used in each song, and now this is possible with CDLC as well.

Well, that is actually quite nice! :)

 

Anyway, when there are new features like this added to the Toolkit, it would be a great idea to actually tell people about it!

You see, in most cases the update notes showed in the Toolkit tell me nothing, because they are so short. And in case they are longer, the rest of the text is always clipped off because there is no line break in the updater window.

 

Maybe this would be complicated to do in the updater itself because it is linked to github and you don't want super long commit titles... but instead you could develop the habit to leave a note here in this thread (or on the first page) to post the changelog and give a short explanation where useful, e.g. when new features are added.

well I can't remember everything :D
So I'll post here valuable improvements on what's was changed, kk

Is it just me, or does it take everyone  that long to open the Tone window. It takes my computer 10 seconds (I measured it) to open that window after clicking on Add or Edit. I've had this problem before, and creating a new install of the toolkit fixed it, but that didn't work this time.

I don't have any issue of that kind on both of my PC (one running W8 and the other running W7).

OK, we have some things done, like automatic audio conversion for RS2014 or RS1 to RS2014 autoconversion, and fixed bug with old RS1 songs arrangement import.

@@Alex360 Thanks for posting here  :D So this means we don't have to work through Wwise anymore?

This is fucking awesome!!! I have to look up all the settings everytime I convert a new song. It is the most annoying part of the whole process, and now this is completely gone?

 

I ran into a problem, though:

When I choose the .wav audio file, I get the error "Could not find WwiseCLI.exe or Audiokinetic directory" upon pressing "Generate". Then the Toolkit closes, which is quite inconvenient.

 

I found two WwiseCLI.exes on my computer:

"C:\Program Files (x86)\Audiokinetic\Wwise v2013.2.5 build 4845\Authoring\Win32\Release\bin\WwiseCLI.exe"

"C:\Program Files (x86)\Audiokinetic\Wwise v2013.2.5 build 4845\Authoring\x64\Release\bin\WwiseCLI.exe"

 

Also: What exactly does the quality number 0-9 depend on and what settings do you recommend (when the quality of the audio is not unknown)?

Wwise defaults to quality 4, which is 128kps (stereo) so I would suggest using that if you've always just used default in Wwise before.  I like using quality 9, which is the equivalent of 320kbps (stereo).

 

The auto conversion will be a script (correct me if I'm wrong Alex :D) that uses Wwise, so you'll still need it installed.  Cozy made I think, check out his automatic MIDI to RS14 custom thread.

 

And @SmellyOrc, my pc opens those boxes instantly.  Never had any trouble like that, but I do not auto update the toolkit and I can't remember which version I'm on.

Maybe we've got some things untested and couple bugs here an there, but we're working on it, it's just beta features, it probably fail under MAC and so on, but it's only cozy and me who looking in to, and I'm slow as hell xD

@@Alex360

I only wanted to report the problem I faced as a bug to help your development - I am aware this is beta and I am not expecting it to work perfectly after the first release ;)