Latest restricted WACUP beta release is build #14278/14282 (January 23rd/24th 2023) (x86 & x64 changelogs) | Latest WACUP public preview is build #7236 (March 11th 2021) (x86 only)

NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Recent Posts

Pages: [1] 2 3 ... 10
1
Skins / Re: WACUP Refugee (Last updated: August 17th 2021)
« Last post by dro on Today at 12:31:35 AM »
Quote from: Aminifu on Today at 12:06:56 AM
My configuration of WACUP beta version 1.8.18.14278 crashes as soon as I try to use Refugee-Declassified v1.30. I get a message telling me the x86 version (#14278) is not current and offering to update to the x64 version (#14282) of WACUP. That version is too incomplete for my needs.
Build #14282 is an x86 only update & not an x64 build (which is still only at #14278). Build #14282 specifically fixes the modern skin related loading issues that #14278 had. If it's trying to install the x64 build then I'd need more details as I don't see that happening from the versioning details that the build is provided to download & it prompting to update to a newer build after a crash is intended to avoid me seeing a load of crashes from a build that's already been fixed.

-dro
2
Skins / Re: WACUP Refugee (Last updated: August 17th 2021)
« Last post by Aminifu on Today at 12:23:27 AM »
Wow, thanx for the quick reply. Who's Classic Modern and which version? The one I use doesn't cause a crash, but the window locations are not saved between sessions.

All the other modern skins I use don't have these issues. I'll wait to see what happens with the next beta release before reporting this to dro.
3
Skins / Re: WACUP Refugee (Last updated: August 17th 2021)
« Last post by Samey the Hedgie on Today at 12:18:28 AM »
Latest seems to have problems with the more demanding modern skins. Classic Modern had crashing issues too, from what I heard on the Discord server.

I'd just use either classic skins or a less 'demanding' modern skin like Bento until the next build is released.
4
Skins / Re: WACUP Refugee (Last updated: August 17th 2021)
« Last post by Aminifu on Today at 12:06:56 AM »
My configuration of WACUP beta version 1.8.18.14278 crashes as soon as I try to use Refugee-Declassified v1.30. I get a message telling me the x86 version (#14278) is not current and offering to update to the x64 version (#14282) of WACUP. That version is too incomplete for my needs.

Refugee-Declassified v1.30 worked fine with the previous WACUP x86 beta version configured the same way the current version is.
5
General Discussion / How to manually setup WACUP to use your own Twitter App API keys
« Last post by dro on Yesterday at 01:41:41 PM »
How to manually setup WACUP to use your own Twitter App API keys

To setup WACUP to use your own Twitter App API keys for sending tweets instead of using the WACUP App API keys, please follow the steps below.

If you are uncertain of what you are doing or only occasionally send tweets then you should ask in the forum or prefer to keep using the WACUP handling (assuming recent changes to how Twitter & access to it's API are e.g. if it's gone to a paid model).
  • Goto Preferences -> Advanced
  • Change 'WACUP' to 'User App' from the drop down
  • Goto Preferences -> Playback -> Play Tracking -> Select the 'Twitter' tab
  • Click on the 'Twitter App' link or go to L"https://apps.twitter.com/ to create a Twitter App
    - Please follow the instructions that Twitter provides on how to create a valid Twitter App.
    - If you have created a Twitter App you want to use then please skip this step
  • Once the Twitter App is created, goto the part of the Twitter App page which shows your keys
  • Copy the 'Consumer Key (API Key)' and the 'Consumer Secret (API Secret)' values and paste them into the same field on the preference page from step 3
  • Click 'Encrypt & Save' to store the keys
    - If you make a mistake and you want to change or re-enter the keys, on the Preferences -> Advanced page, changing the drop down from 'User App' to 'WACUP' and back to 'User App' will reset things so you can then go back to step 3
  • The preferences page will have now been reloaded and changed to ask for the user credentials to tweet for
  • Follow the instructions provided on the preference page to authorise tweeting for the required Twitter user
  • You should now be able to tweet to the desired user using your Twitter App API keys :)
-dro


Note: This is re-posted from the beta sub-forum & has been done in response to reported pending changes to access to the Twitter API which will likely put it all behind a paywall. If that happens then it's going to prevent the WACUP feature from working like it has been since it was first implemented years back but thankfully I put in place a means to use your own Twitter App api details.

I'll be keeping an eye on how this plays out as at the time of this post there's no information on what the cost is going to be as I'd prefer not to pay Twitter considering this is a cash grab but I'm also aware that there are those making use of the feature who'd not be able to use it.
6
Skins / Re: Big Bento Modern v1.2
« Last post by dro on January 31, 2023, 05:08:46 PM »
There's now a generic patch in place for the next beta build to deal with the file existence checks that'll do what's needed irrespective of the file existing or not.

-dro
7
Skins / Re: Big Bento Modern v1.2
« Last post by dro on January 28, 2023, 11:17:12 PM »
It's not just BBM that has this issue & there's old versions of the skins that I know are being used which are still affected. So even with a better implementation for the skin, I've still got to make changes on the core side to deal with this.

Really I need to find a way to provide a proper skin script call to use to check than all of these file existence checks as they don't work 100% but that still involves the skins being updated & means the old ways need to be dealt with.

-dro
8
Skins / Re: Big Bento Modern v1.2
« Last post by Eris Lund on January 28, 2023, 10:44:44 PM »
I could provide a patch for BBM with the version check I do for DeClassified (as seen here), only with Victhor's OK
9
Skins / Re: Big Bento Modern v1.2
« Last post by dro on January 28, 2023, 10:31:36 PM »
Ah, I see what's going on. I'll need to edit the patching that's done on the skin version checks to avoid that (really can't remember why that file got picked with this skin for "winamp" vs wacup version detection).

-dro
10
Skins / Re: Big Bento Modern v1.2
« Last post by Der_Rio on January 28, 2023, 08:54:21 PM »
OK. I couldn't reproduce the "use OS registry" method.  :-\

So, I made a backup of my WACUP_portable folder. Then I deleted it and reinstalled latest WACUP as portable (full install). But again, no "Integrated Waveform Seeker (IWS)" option!  :o
Then I copied bit by bit from the backup to the new install.
That way I found out what was the problem:
There has to be a file
WACUP_portable\Settings\WACUP_Tools\koopa.ini
It doesn't matter what's in the file - even a 0 byte file does it.
If that file is missing (or renamed) then there is no IWS. If I recreate a file with that path and name, the IWS reappears.
100% reproducible on my system.

Rio  :)  ???
Pages: [1] 2 3 ... 10