Jump to content

Kaijin

Member
  • Posts

    316
  • Joined

  • Last visited

  • Days Won

    7

Other groups

Member

Kaijin last won the day on May 29 2015

Kaijin had the most liked content!

About Kaijin

  • Birthday 02/28/1978

Contact Methods

  • djkaijin

Profile Information

  • Gender
    Male
  • Location
    Portugal
  • Interests
    Music, Music & Music

    https://www.youtube.com/DjKaijin
  • Guitar
    Ibanez S520-WK
  • Bass
    Harley Benton B-250

Recent Profile Visitors

6,176 profile views

Kaijin's Achievements

Community Regular

Community Regular (8/14)

  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

944

Reputation

  1. Happy Birthday Kaijin!

  2. Happy Birthday Kaijin!

  3. I'm not being ridiculous and it's pretty obvious that nobody else sees this matter the way I do. I played here for fun, but that's not happening anymore, so I won't cause any more troubles and none of you have to deal with "madness". Cheers.
  4. I'm gonna be very short about this and if nobody else agrees with me, I totally understand, but I don't change my mind and if the majority of members see fit, I won't even play in the CS anymore. I don't tolerate custom adoptions, specially when it comes to Glen's customs. Many bad things have been said and done because nobody ever respected Glen's work and they just simply stole his customs before the adoption system was "launched" and those people released the customs like they were their own work. That's childish, stupid, only shows lack of character and I could go on and on. I hate people like that and I can only stand being around them because I totally ignore them and those same people are only a few (fortunately). I thought that this had stopped, since Glen doesn't post a custom here for a long, long time, but to my total surprise I'm still seeing the same way of thinking towards the customs stolen in the past, which only leads me to believe that the point of view of those people stays the same. Btw, if I see one of Glen's latest customs posted ONLY on my site, shared on any other site (this or another one), the member responsible for doing that without permission can be assured that will be discovered and banned, since I gave Glen my word that his latest customs wouldn't be used and abused like the other customs in the past. If you guys decide that because of this it would be awkward to have me around playing in the CS, just make a post saying so, or send me a PM and I won't participate anymore. Thanks
  5. In Portugal it's also very hot, in some regions of the country today the temperatures went to 40ºC-42ºC. When the temperatures here are above 30ºC, I can't play during the day, my room gets extremely hot and there's no AC here :(, so I have to wait for the evening when the temperature gets much lower (18ºC-20ºC) and then I can play without sweating all over the guitar/bass :lol:
  6. Thanks, but I'm not doing anything special, just trying to help in any way I can. :) As I said in the other post, I'm not a dev, but posting the error can help to pin point the source of the problem faster and easier, so I would say that yes, even if I can't "read" the error properly, I can always send a PM to @cozy1 or @Alex360 and they'll explain to me and if my knowledge is enough, I can help solving the issue, if not, one of them will know for sure how to do it. Thanks
  7. Sorry, I forgot to mention 1 detail that might or not make a difference when importing the package with the toolkit. In the toolkit configuration, do not select "Imported Structured Packages". In terms of the importing it's the same, the difference is the files that the toolkit creates when importing a .psarc and in my own experience, I had some customs for PC that if imported with the option selected gave me an error, I removed the option and they imported fine. I'm not a dev, I just help testing the toolkit when the devs need, I only report issues that I find, so the information I post is 99% based on what I've learned from my own experience with the toolkit on PC, so it might not apply to other platforms, but it doesn't "hurt" to give it a shot. :) If any other members using the MAC version of the toolkit have similar or other problems, if @@missis sumner doesn't mind, feel free to post your issues on this thread and I'll try to reply the best way I know and if necessary, I can report the issues to the devs, since they already have plenty on their "plate", this is the least I can do to help them out, since they do an amazing job always improving the toolkit and solving bugs/issues that users encounter.
  8. Alright @@missis sumner, good to hear that. I was going to say..... "If you need older toolkit versions, the oldest I have is from 2015-02-10", but while typing I realized you need a MAC version, not PC.... *face palm*..... I'm still recovering from being sick, sorry about that :blush: If you encounter difficulties converting any custom in the future from PC to MAC, you can send me a PM, which is much faster for getting in contact with me, because sometimes I don't log on the forum for a couple of days, while the email notifies me every 15 minutes, so it's always faster. :)
  9. Instead of using the "Converter" tab of the toolkit @@missis sumner, try to "Import Package" in the "Creator" tab and don't change anything after the _p.psarc is imported except for the platform (remove the check box from PC and click on MAC). Click "Generate" and you should get a working _m.psarc. Let me know if that worked for you.
  10. Later this week...that run was hard enough, let alone dealing with the lag of Fraps.. I have another idea i might try for video recording as well :3 Yeah, try to record just a soda can, that would suit your personality really well :lol:
  11. I know this week ended several hours ago, but I've been sick for the past 2 days and I didn't even had strength to post the screenshots. Anyway.... BG: http://s6.postimg.org/rn6rqfxw1/RS2014_CF_Championship_Week_87_Bass_BG_1_100.jpg http://s6.postimg.org/n2p6p93kh/RS2014_CF_Championship_Week_87_Lead_BG_1_87.jpg http://s6.postimg.org/p8jhjr70x/RS2014_CF_Championship_Week_87_Rhythm_BG_1_97.jpg IM: http://s6.postimg.org/6u8yfruq9/RS2014_CF_Championship_Week_87_Bass_IM_1_99.jpg http://s6.postimg.org/cjp7030wh/RS2014_CF_Championship_Week_87_Lead_IM_1_86.jpg http://s6.postimg.org/9qvzg20k1/RS2014_CF_Championship_Week_87_Rhythm_IM_1_92.jpg ADV: http://s6.postimg.org/6y2rw107l/RS2014_CF_Championship_Week_87_Bass_AD_1_99.jpg http://s6.postimg.org/opeeahfm9/RS2014_CF_Championship_Week_87_Lead_AD_1_85.jpg http://s6.postimg.org/r803b61ch/RS2014_CF_Championship_Week_87_Rhythm_AD_1_95.jpg MC: http://s6.postimg.org/cdbhwzrrl/RS2014_CF_Championship_Week_87_Lead_MC_1_83.jpg
  12. Yes @@cozy1, I don't add anything, neither arrangements or tones, I leave everything as it is when the toolkit imports the .psarc file, the only "modification" is adding NDD to the title of the song and removing DD from the .xml(s). When I pack my own customs, where I have to add tones and arrangements, the last 3 I did all had tone changes and I didn't experienced none of what's described in the posts above. Since I never add DD to my customs, I only use DDC to remove DD, that's why I only can confirm the issue when removing DD, I have no idea if the same issue might happen when adding DD to a custom using the method I described to remove it. I wasn't sure about what could be the cause, but after reading your post I'm leaning towards something related with DDC, instead of the toolkit. Since I usually remove DD from customs every week (because of the songs selected for the championship that have DD), I'm pretty sure that this will happen again and when it does, I'll take screenshots and make a detailed post with step by step. Btw, I forgot to mention on the previous post, the error window I get when the issue happens is almost the same as the one posted by @@SmellyOrc on post nº 381.... I can't be sure of the entire text, but the 1st 5 lines are the same or very similar. Thanks.
  13. Try this one https://mega.co.nz/#!CQZGmJTB!ZjBzJJi2RLHEXCdQdWeLL8bHZG0uo3cbFzFoEqXe7yA I don't have a Mac, so I can't test it. Also, I removed DD from my PC version, I hope you don't mind.
  14. Hey guys, I've been away for a while and I was trying to catch up on this thread..... so many posts in a short period of time. Anyway, I read the last posts talking about tone issues with the toolkit, but from what I gathered, you were just talking about changing tone names or the order of the tones.... Well, I've experienced an issue related with tones when removing DD (I don't know if the same happens when adding DD to a custom). Unfortunately I didn't take any screenshots when the issue occurred, since it was just a few times, but given the "line of posts", here's the situation (I'll take screenshots on the next custom that this happens)..... 1st I should describe the method I use to remove DD from a custom. I import the package in the toolkit. Once the toolkit is finished and I have the custom imported, I add the letters "NDD" to the end of the title of the song, go to the DDC tab, select the .xmls inside the "arr" folder created by the toolkit when imported the package, Ramp-up model "ddc_dd_remover", Config File "ddc_default", Phrase length "40" and I click the check box "Overwrite original files" (that way I don't have to add the NDD arrangements and remove the DD ones on the "Creator" tab) and click "Remove DD". This is what I've always done and it always worked perfectly. I don't know which build of the toolkit started to do what I'm going to describe next, but it must be one of the latest builds, since this only happened recently, in the last month, maybe 2. So, I do everything I described above but when I click the "Generate" button to create the _p.psarc file, I receive an error and all the times I read something related to the tones. Every time this happened, the behavior is always the same and I was "lucky" to discover why I was getting the error after removing DD, since that never happened before and this only happens on customs that have tone changes. For some reason, DDC changes the names of the tones on the lines that have the tone time code in the .xml(s) When I look above, where it's set ToneA, ToneB, etc., the names are correct, but DDC changes the names after that, on the lines with the time codes. Since this happened 4 or 5 times so far, the only thing I find in "common" is that DDC replaces the names on the lines with the time codes for the "Tone type" name of the tone. For example, a tone called "tone_dist", where the tone type is "Distortion", the unpacked xml has all the names correct, after removing DD with DDC, the name that shows on the line with the time code is "Distortion", instead of "tone_dist". To demonstrate (this is just an example I manually edited to reflect what I described).... This: <tonebase>IKYRH_lead</tonebase> <tonea>IKYRH_lead</tonea> <toneb>IKYRH_delay</toneb> <tones count="2"> <tone time="375.924" id="0" name="IKYRH_delay" /> <tone time="388.624" id="0" name="IKYRH_lead" /> After removing DD show this: <tonebase>IKYRH_lead</tonebase> <tonea>IKYRH_lead</tonea> <toneb>IKYRH_delay</toneb> <tones count="2"> <tone time="375.924" id="0" name="delay" /> <tone time="388.624" id="0" name="distortion" /> Every time this happened, I just replaced the incorrect names on the tone time line(s), clicked "Generate" in the toolkit and the _p.psarc is generated without any error. Just thought you guys should know this is happening and I don't know if this is related with the toolkit or DDC. As soon as I have another custom that this happens, I'll take screenshots and make a more detailed post. Thanks again for everything, as always. :)
  15. 2 updates.... Lead ADV: http://s6.postimg.org/5aj8s3m8h/RS2014_CF_Championship_Week_86_Lead_AD_2_84.jpg Rhythm MC: http://s6.postimg.org/vk8womxjl/RS2014_CF_Championship_Week_86_Rhythm_MC_2_92.jpg
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy