kanor

If ur playing the game on ur main computer chances are u got a lot of background processes like antivirus, browser tabs, torrent, chat apps, etc. These things that run in the background may cause spikes in CPU or RAM usage and will cause occasional stutters. Best to get a cheap/older computer that will be ur dedicated computer for playing the game. DDR ain't power hungry anyway.

Cuz the software is programmed to to determine the Cabinet Type of official hardware Then it makes the adjustments automatically The game can't determine the Cabinet Type cuz we are using unofficial hardware so it will default to an SD cabinet type That's why we have to manually hack it using hex edits

Hmmm... This ain't no clean data, it's a Frankenstein package songs are conversions not original data rip DLLs are from previous updates ...but good job nonetheless

I see, looks like you haven't been here for long. Those "spam messages" used to be very helpful messages but he wiped them out and replaced with that message.

That's what I actually said: it won't work. It doesn't work that way that you load an October-dated DLL to a September set of patches.

Chill bruh, not sure how long u'v bn here to know @topet2k12001 but that guy is awesome. Don't hate. This is his thread anyway. Too bad that's the only part u saw abt him. Was one of the most helpful and skilled guys I've seen.

Lol...I hope u realize ur reacting to a post dated in 2020...

Oh my God. Of course loading an October DLL to a September patcher won't work. It doesn't work that way ever. Not sure who gave ppl the idea that it can work like that. Oh my God again. Dunno where you got that info but y'all know that u can do right-click->Inspect Source to see the details of what a patcher does. And then you can compare them against each other Left: xinrin RIght: Lupinthidr They're the same.

Ya but don't expect them to work as event songs anymore if you do that. This is another obvious way to tell if the data is clean or tampered.

...and this is the reason why I said in another previous post that it's actually pointless to clean the DLL if you're just going to forcibly unlock the unlockable songs. Cleaning the DLL brings everything back to their original state. You can manually unlock the songs straight from within startup.arc if you want. Or...simply "port" the songs (add them back) to the previous working update - which is what @Curilang and his friend SchneiderAFX already did, here. AFAIK only @topet2k12001's fork of butterfly is developed enough to fully and properly support in-game events of DDR. I'm pretty sure MonkeyBusiness and Asphyxia are capable of doing that too, but nobody is developing them actively.

Nothing strange there. People are forgetting..."clean" means "everything in its original state" = songs that are supposed to be locked, are locked.

Fixing the DLL without a server that supports the Galaxy event will be just a waste of time and effort If y'all just wanna play the newest songs just port 'em to the previous update build and force unlock those songs The "troll" mods are random bastardization of the DLL..it's not like those are "features" that qualify being added to those patchers lol...

Cleaning up the DLL is only half of it. Y'all know that the server ur using needs to support whatever event. Y'all know that only @topet2k12001 and friends working on butterfly can make this happen. Too bad he got pissed with all the leaks. This was a very nice thread back then.

Dude read the announcement. It will answer your question.

The answers you are looking for are already in this thread; you will just need to read.

Which arc files?

So...towards the end of the log (usually that's where you'd want to look first because the last few lines, before the game crashes, is where it would indicate something), I saw this (highlighted in red), something has "failed" and you can see it below (with "F" at the start). [2020/07/20 18:46:26] M:xrpc: tax.get_phase result make/pkt/resp/fin/comm=32/33/10/1/24302 [2020/07/20 18:46:26] F:saveXML: libXml : save file failed. [2020/07/20 05:46:28] W:signal: exception raised: EXCEPTION_BREAKPOINT [2020/07/20 05:46:28] I:signal: printing callstack [2020/07/20 05:46:28] I:stackwalker: 6FA74880 (libavs-win32): (unknown): XCd229cc000099 [2020/07/20 05:46:28] I:stackwalker: 10019911 (arkmdxp3): (unknown): arkHeapDebug [2020/07/20 05:46:28] I:stackwalker: 10018825 (arkmdxp3): (unknown): arkHeapDebug [2020/07/20 05:46:28] I:stackwalker: 1001A470 (arkmdxp3): (unknown): arkHeapDebug [2020/07/20 05:46:28] I:stackwalker: 1000FCC9 (arkmdxp3): (unknown): arkGetTickTime64 [2020/07/20 05:46:28] I:stackwalker: 10002447 (arkmdxp3): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 10096D6B (arkmdxp3): (unknown): arkMDXUpdate [2020/07/20 05:46:28] I:stackwalker: 5EF382B5 (gamemdx): (unknown): gameMain [2020/07/20 05:46:28] I:stackwalker: 5EF32C2F (gamemdx): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 5F03AEC1 (gamemdx): (unknown): gameMain [2020/07/20 05:46:28] I:stackwalker: 5F03A6EF (gamemdx): (unknown): gameMain [2020/07/20 05:46:28] I:stackwalker: 5EF3326C (gamemdx): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 5EF33404 (gamemdx): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 5EF33888 (gamemdx): (unknown): gameMain [2020/07/20 05:46:28] I:stackwalker: 10001DFA (arkmdxp3): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 100030CD (arkmdxp3): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 00449E8F (spice): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 0071E910 (spice): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 00401386 (spice): (unknown): (unknown) [2020/07/20 05:46:28] I:stackwalker: 76476359 (KERNEL32): (unknown): BaseThreadInitThunk [2020/07/20 05:46:28] I:stackwalker: 772A7C24 (ntdll): (unknown): RtlGetAppContainerNamedObjectPath [2020/07/20 05:46:28] I:stackwalker: 772A7BF4 (ntdll): (unknown): RtlGetAppContainerNamedObjectPath [2020/07/20 05:46:29] F:signal: end [2020/07/20 05:46:29] I:launcher: stopping subsystems [2020/07/20 05:46:29] I:logger: stop [2020/07/20 05:46:29] I:rawinput: disposing devices I also noticed this in the first 3 lines of the log: [2020/07/20 05:46:19] I:launcher: SpiceTools Bootstrap (x32) [2020/07/20 05:46:19] I:launcher: 1.0-V-2020-06-15T22:40:42 [2020/07/20 05:46:19] I:launcher: arguments: -exec arkmdxp3.dll -exec arkmdxp3.dll -k ddrhook.dll -k ddrhook.dll -netfixdisable -netfixdisable -ddr -ddr -io -io -h 33554432 -h 33554432 Can you try the following: In spicecfg.exe, in the "Options" tab...remove all checked/enabled/entered figures. Looks like ddr.exe is already configured with those options so, when you enabled the same options in spicecfg.exe, we now see double-entries of those options. Right-click on butterfly.sqlite (the file that got generated earlier). Check/enabled "Read Only" and press OK. And then repeat (right-click on butterfly.sqlite) and then uncheck/disable "Read Only" and then press OK again. Make sure no system/game files are open (from the game folder). Open your "spicetools.xml" and in the "options" section, double-check that indeed all options are turned off (don't worry, ddr.exe will "invoke" those options whenever you run the game through it). Restart the computer, and then give it another try. During the game "Settings Check" screen (the black screen) try to interrupt it by going to the Service Menu. If you are able to do so, please double-check and set the clock (to your local/PC time).

Um, could you attach it here instead? It would be easier for us that way instead. Logs are safe to share, don't worry. They get replaced anyway everytime you play.

In the game folder there's a file named log.txt. Please share it to us.

It crashed only/probably because you were screen recording it. I say "probably" because I have experienced the same with a some screen recording apps. Butterfly "listens" on "Port 80" and some screen recording apps "lock" that port too, causing the crash. Try it again but this time don't screen-record it. And then let us know. But at least, as far as the script working, looks like it's working just fine. I see the required files now in the video. The first time you start the game, you only register a username and PIN. You exit the game after that. And then run ddr.exe again.

Totally. But...you know (ah well...) Anyway. All good sir, no worries.

Hi @Bloodwraythe, I commented on your video. So at around 1:27...that particular command window that closed...that's the butterfly server. It's supposed to stay open throughout your play session (you only close/exit it after you play and exit the game). But, it closed unexpectedly. @tw3nz0r may be right, it could be that you don't have Java installed (minimum version 8). https://java.com/en/download/ @topet2k12001 I think you need to add a "checking mechanism" in the script to check if the user has Java 8 installed and if not, exit the script.

There are files missing in your game folder. Files that "ddr.exe" is supposed to generate. I can't see them in the screenshot. You're missing: butterfly.exe - this gets "generated" by ddr.exe butterfly.sqlite (it gets generated when you run ddr.exe for the first time) - this gets "generated" by butterfly.exe (which runs automatically as part of running ddr.exe) butterflyserver-1.2.0-20200705.jar - this gets "generated" by butterfly.exe (which runs automatically as part of running ddr.exe) card0.txt - you forgot to configure this in spicecfg.exe (spicecfg.exe is going to generate a "card' for you) card1.txt (optional) - for Player 2 EXPLANATION: The file "butterfly.exe" is the "emulated e-Amusement server" so if it's not running then your game will be "offline" or "disconnected from the network" hence you are seeing that error message at the start screen. And based on the screenshot you provided, I can't find butterfly.exe and its related files. It could be caused by either you not clicking on "Yes" during Windows UAC (User Account Control) - that pop-up that typically appears when you run/launch an .exe file. Or...it could be caused by an incomplete configuration where you forgot to configure your "cards" from spicecfg.exe. If possible/if you can: keep that same window (the screenshot below) maximized...then run ddr.exe. And screen-record the entire process as it happens. But keep that window in plain view so that we can see whether the needed files are getting generated. Or just put the command window and that Explorer window side-by-side so that both can be seen during the screen recording.

If you mean those "intentional leaks" perhaps, yes...but not software leaks like these arcade data games in this forum site. The leaks here are "true-definition" leaks and not "marketing-related" leaks.

@NoctsRanun the term "leak" is often associated with, or denotes, a "deliberate" disclosure (of information or data or whatever). That's why @tw3nz0r has it correctly when he said "it depends on when someone decides to share." The "decides to share" part is the key component to the meaning of a "leak" because that is what constitutes the "deliberate" disclosure of the information. So, technically a "leak" is a "breach" of something that should not have been divulged. I understand that in daily social media lingo/talks, people nowadays talk of a "leak" as something that's "an okay thing" that people talk about publicly, and as if it is supposed to happen at regular time intervals (for example, "leaks" about the next smart phone model from brand xyz). I think the term and context got romanticized/glamorized through the years and has gotten out of context. Sometimes, information is "leaked intentionally" as a marketing strategy (to create "buzz"). But that's a different discussion altogether.