Messages

1

Melty Blood Auditorium / Re: Next major feature for CCCaster

« on: April 24, 2013, 11:00:02 PM »

Does caster open MBAA.exe in high CPU priority? If not, could you?

You can download third party software to save your priority changes. "MBAA.exe" will run at high automatically when started.

Yes, and I can also make it start automatically on high by going to cmd.exe and typing in "start /high mbaa.exe". Caster would open up MBAA.exe on its own, so a third party app could do it if you have a process continuously running and monitoring when the MBAA.exe process comes up. But who wants that?

2

Melty Blood Auditorium / Re: Next major feature for CCCaster

« on: April 23, 2013, 10:53:46 PM »

Does caster open MBAA.exe in high CPU priority? If not, could you?

3

Melty Blood Auditorium / Re: CCCaster v1.0a - Netplay client for MBAACC 1.4.0

« on: April 16, 2013, 03:07:30 PM »

It's crashing whenever I connect to someone or someone connects to me. Windows reports that the application has stopped working. It's probably how it's trying to open up MBAA.exe. I'm using Windows 8 (yes I know). Some logs for you

Code: [Select]

Faulting application name: cccaster.exe, version: 0.0.0.0, time stamp: 0x516cce30
Faulting module name: cccaster.exe, version: 0.0.0.0, time stamp: 0x516cce30
Exception code: 0xc0000005
Fault offset: 0x00011b1e
Faulting process id: 0xd30
Faulting application start time: 0x01ce3af622b817f3
Faulting application path: C:\MBAACC\cccaster.exe
Faulting module path: C:\MBAACC\cccaster.exe
Report Id: 675c0a74-a6e9-11e2-bf24-bc5ff43921d2
Faulting package full name:
Faulting package-relative application ID:

Code: [Select]

Fault bucket -760711535, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: cccaster.exe
P2: 0.0.0.0
P3: 516cce30
P4: cccaster.exe
P5: 0.0.0.0
P6: 516cce30
P7: c0000005
P8: 00011b1e
P9:
P10:

Attached files:
C:\Users\Michael\AppData\Local\Temp\WER2D30.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Michael\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_cccaster.exe_acdf2b1285a6dfdac6ef234407e1bff3b298545_110f92a0

Analysis symbol:
Rechecking for solution: 0
Report Id: 675c0a74-a6e9-11e2-bf24-bc5ff43921d2
Report Status: 0
Hashed bucket: 7892a73b395412f50861032869d51dbe

Code: [Select]

Version=1
EventType=APPCRASH
EventTime=130106268176395796
ReportType=2
Consent=1
UploadTime=130106268176777107
ReportIdentifier=675c0a75-a6e9-11e2-bf24-bc5ff43921d2
IntegratorReportIdentifier=675c0a74-a6e9-11e2-bf24-bc5ff43921d2
WOW64=1
NsAppName=cccaster.exe
Response.BucketId=7892a73b395412f50861032869d51dbe
Response.BucketTable=1
Response.LegacyBucketId=-760711535
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=cccaster.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=516cce30
Sig[3].Name=Fault Module Name
Sig[3].Value=cccaster.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=516cce30
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00011b1e
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=5861
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=5861822e1919d7c014bbb064c64908b2
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=f3d5
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=f3d5be0cad2787556264647dc02181c3
UI[2]=C:\MBAACC\cccaster.exe
UI[3]=cccaster.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\MBAACC\cccaster.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\MBAACC\pthreadGC2.dll
LoadedModule[5]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[7]=C:\Windows\SYSTEM32\WINMM.DLL
LoadedModule[8]=C:\Windows\SYSTEM32\WS2_32.dll
LoadedModule[9]=C:\MBAACC\SDL.dll
LoadedModule[10]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[11]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[12]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[13]=C:\Windows\SYSTEM32\NSI.dll
LoadedModule[14]=C:\Windows\SYSTEM32\ADVAPI32.DLL
LoadedModule[15]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[16]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[17]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[18]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[19]=C:\Windows\system32\IMM32.DLL
LoadedModule[20]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[21]=C:\Windows\SYSTEM32\nvinit.dll
LoadedModule[22]=C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\detoured.dll
LoadedModule[23]=C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\nvd3d9wrap.dll
LoadedModule[24]=C:\Windows\SYSTEM32\SETUPAPI.dll
LoadedModule[25]=C:\Windows\SYSTEM32\CFGMGR32.dll
LoadedModule[26]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[27]=C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\nvdxgiwrap.dll
LoadedModule[28]=C:\Windows\system32\uxtheme.dll
LoadedModule[29]=C:\Windows\SYSTEM32\HsSrv.dll
LoadedModule[30]=C:\Windows\SYSTEM32\DSOUND.dll
LoadedModule[31]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[32]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[33]=C:\Windows\SYSTEM32\POWRPROF.dll
LoadedModule[34]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[36]=C:\Windows\SYSTEM32\DINPUT.DLL
LoadedModule[37]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[38]=C:\Windows\SYSTEM32\WINTRUST.dll
LoadedModule[39]=C:\Windows\SYSTEM32\CRYPT32.dll
LoadedModule[40]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[41]=C:\Windows\system32\napinsp.dll
LoadedModule[42]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[43]=C:\Windows\system32\NLAapi.dll
LoadedModule[44]=C:\Windows\System32\mswsock.dll
LoadedModule[45]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[46]=C:\Windows\System32\winrnr.dll
LoadedModule[47]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[48]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[49]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[50]=C:\Windows\System32\rasadhlp.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=cccaster.exe
AppPath=C:\MBAACC\cccaster.exe
NsPartner=windows
NsGroup=windows8

4

Regional Community / Re: The Pacific Northwest! Washington, Oregon and Idaho Players

« on: March 21, 2013, 01:45:36 AM »

To anyone in Oregon, we actually have a scene centralized at OSU and Corvallis, although a few are coming up to Portland for a couple terms.

If anyone wants to come, OSU is having a LAN soon which majority of our Melty scene is going to: https://www.facebook.com/events/316756781760625/

5

Regional Community / Re: The Pacific Northwest! Washington, Oregon and Idaho Players

« on: August 07, 2012, 10:36:43 AM »

I play. I'm around Portland/Clackamas until September 21. Then I'll be in Corvallis.

6

Regional Community / Re: The Pacific Northwest! Washington, Oregon and Idaho Players

« on: January 31, 2012, 11:12:00 AM »

Oregon feels soooo dead. I managed to get three people at Oregon State to try and pick up Melty. I just doubled the Melty player size at Oregon.

OSU's having a LAN party March 2-4 weekend, no details yet. But I can almost guarantee you it'll have SSF4. It's not Melty, but I'll be there with my computer and stick to play anyone that wants to.

7

Melty Blood Auditorium / Re: The MB:AA:CC:PC thread: Trial out! Get that key rebind tool!

« on: December 30, 2011, 07:13:21 PM »

I just played some netplay with a friend of mine. We had about a 20-30 ping to each other and the game chose a delay of 1, but the game lagged horrifically during the character select and randomly during the fighting. Does anyone know if we can manually select the delay or increase it?

8

Regional Community / Re: The Pacific Northwest! Washington, Oregon and Idaho Players

« on: November 08, 2011, 11:41:39 PM »

Hollar at Corvallis/OSU area. MBAACC to PC, let's get some local netplay going on when it comes out.

9

Regional Community / Re: The Pacific Northwest! Washington, Oregon and Idaho Players

« on: August 06, 2010, 09:01:49 PM »

No kidding, there's no MBAA scene at OR. Everyone here plays SSF4 (which ain't that bad).

There was a MBAA scene here.  I think I scared them all off.

In all seriousness though, do any of you guys live in the Portland area?  I'm down for some games at some point.

Clackamas is close, but I'm travelling over seas for a month, then heading to OSU after that. No bueno from me.

10

Regional Community / Re: The Pacific Northwest! Washington, Oregon and Idaho Players

« on: July 18, 2010, 08:38:30 PM »

No kidding, there's no MBAA scene at OR. Everyone here plays SSF4 (which ain't that bad).

11

Akiha's Tea Room / Re: Introductory Thread (Take off your shoes, please)

« on: July 12, 2010, 11:43:52 AM »

Hey guys, I was an MBAC player a year back, but quit when MBAA came out. I play Nero, which seems to be a taboo around here. I remember going on the IRC and playing a Ciel player and losing 5-2, but that was a long time ago. Only decided to register now after I got hyped up from watching the EVO finals.