EXCEPTION_ACCESS_VIOLATION

User-to-user help and troubleshooting.
Dorjan
Posts: 5024
Joined: Sun Oct 07, 2007 9:56 am
Location: England

Post by Dorjan »

All I can say is OMG WYLD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

WB if you remember me at all that is :)
I decided to relive the days gone by in my new blog.
---
Remember, what I say is IMO always. If I say that something sucks, it actually means "I think it sucks" OK?
Cookie Monster wrote:QUOTE (Cookie Monster @ Jan 31 2012, 03:09 PM) True story.

Except the big about dorjan being jelly, that's just spidey's ego.
ImageImage
raumvogel
Posts: 5910
Joined: Sun Jul 20, 2003 7:00 am
Location: My lawn
Contact:

Post by raumvogel »

They always come back. Alleg is like a home that you left...but had to come back to.
Image
WyldKarde
Posts: 229
Joined: Thu Feb 24, 2005 8:00 am
Location: 127.0.0.1

Post by WyldKarde »

HSharp wrote:QUOTE (HSharp @ Jun 2 2010, 11:18 PM) EDIT: Also try disabling texture pack under graphics options, advanced, use texture pack (ESC->O->A->P) (otherwise known as ACE keypress) try post below first instead actually

---

Also you didn't crop your VideoSettings log did you?

mine looks like

(

Code: Select all

 snipped)

Which looks a bit different to yours as you don't seem to have the 2nd section, this might be part of ze problem.[/quote]

Ok, just dug out the logfile and cutanpasted it in it's entirety:

CODELog file VideoSettings.log created - Jun 02, 19:49

Created D3D9 interface.
Found 1 adapters.
Extracting adapter 0: \\.\DISPLAY1 - NVIDIA GeForce 8800 GTX
800 x 600 @ 60Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 72Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 75Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1024 x 768 @ 60Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1024 x 768 @ 70Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1024 x 768 @ 75Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1152 x 864 @ 75Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1280 x 800 @ 60Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 56Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1440 x 900 @ 59Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1440 x 900 @ 60Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1440 x 900 @ 75Hz [32 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 60Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 72Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 75Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1024 x 768 @ 60Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1024 x 768 @ 70Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1024 x 768 @ 75Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1152 x 864 @ 75Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1280 x 800 @ 60Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
800 x 600 @ 56Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1440 x 900 @ 59Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1440 x 900 @ 60Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]
1440 x 900 @ 75Hz [16 bit]		[HW 1   WND 1   DS 77   AA 0x17]


FOUND RESOLUTIONS (MODE 0) (MAXRATE: 60):
	0) 800x600 @ 60
	1) 1024x768 @ 60
	2) 1152x864 @ 75
	3) 1280x800 @ 60
	4) 1440x900 @ 60
CURRENT IN-GAME RESOLUTION: 1440x900 @ 60

User selected values:
AD 0   MON 0x00010001   WIN 0   VSYNC 0
Fullscreen settings:
FMT 22   W 800   H 600   RR 60   DEP 77
Windowed settings:
FMT 22   W 800   H 600   RR 60   DEP 77
FSMS 2   WINMS 2
MIN 3   MAG 2   MIP 2
Window offset: 0  0

Log closed.


That's since I tried the tutorial under beta tho', so no idea how that interacts with R5.

As for the registry entries, combatfullscreenxsize is 1280, combatfullscreenysize is 1024.

1280x1024?  Strange screen resolution.

Also, Dorj, Raum, great to hear from you guys, but can we not do the hugs and reunion thing in the middle of a tech support thread please?  It kinda gets in the way of my actually getting ingame.  I'll try and save some prox for you both once I'm up and flying again.  :)
--WK
Image
notjarvis
Posts: 4629
Joined: Tue Jun 03, 2008 11:08 am
Location: Birmingham, UK

Post by notjarvis »

Wyld : Sai has put the Beta lobby back up, so if you could try the Beta in-game please (just to check this is fixed with R6). That would be grand
HSharp
Posts: 5192
Joined: Fri Aug 11, 2006 11:18 am
Location: Brum, UK

Post by HSharp »

WyldKarde wrote:QUOTE (WyldKarde @ Jun 3 2010, 02:31 PM) As for the registry entries, combatfullscreenxsize is 1280, combatfullscreenysize is 1024.

1280x1024? Strange screen resolution.
1280x1024 does indeed sound weird, try changing it to 1024 x 768 on regedit (rightclick on CombatFullScreenXSize and select modify, and press decimal and change it to 1024, and it's 400x300 in Hexadecimal terms)
then try up Allegiance (non Beta) and see if that works.

And if your still getting the error can you also tell me what happens if you run Allegiance directly without ASGS to play the training missions?
Image
Image
WyldKarde
Posts: 229
Joined: Thu Feb 24, 2005 8:00 am
Location: 127.0.0.1

Post by WyldKarde »

Ok, I can connect to the beta lobby just fine now, so that's that sorted. Looks like if we fail here I should be ok when R6 goes live.

Just made the recommended registry changes. Gonna go try now and will edit this post when I have a result.

Edit: :cheers: It works! Logged into the main game, set myself up a custom singleplayer round, launched, loaded and undocked just fine. I'm back, baby!

Thanks for the assist, everyone. Especially to HSharp who finally found the glitch. Dunno how the heck that weird@#(! resolution setting ended up in my registry, but now it's fixed and I'm feeling fine.

See you out in the black, amigos!
Last edited by WyldKarde on Thu Jun 03, 2010 4:32 pm, edited 1 time in total.
--WK
Image
ogorass
Posts: 2273
Joined: Fri Sep 16, 2005 7:00 am
Location: Warsaw, Poland
Contact:

Post by ogorass »

WyldKarde wrote:QUOTE (WyldKarde @ Jun 2 2010, 11:21 PM) RAM: 3070MB (Odd, I thought this was a 4 gig box...)
Just chipping in on this little part: You need a 64 bit version of Windows to use anything above 3GB of RAM. You can actually have more physical memory installed, and you probably have, the limitation is because of the maximum address space of a 32 bit OS is, well, 4GB. The 1 GB missing is a sideeffect caused by the fact, that RAM is not the only thing that needs addresses. So yeah, if you want to use the full capacity of your physical memory, upgrade to x64 OS.

OK. Carry on gentlemen.
Image
Image
HSharp
Posts: 5192
Joined: Fri Aug 11, 2006 11:18 am
Location: Brum, UK

Post by HSharp »

No problem, thanks should go to SR-71 though who noticed the problem when Vly was in a similar situation.

It's quite odd though of how your ingame resolution changed, normally you can only change it in fullscreen mode and I thought the default was 800 x 600.
Image
Image
ogorass
Posts: 2273
Joined: Fri Sep 16, 2005 7:00 am
Location: Warsaw, Poland
Contact:

Post by ogorass »

HSharp wrote:QUOTE (HSharp @ Jun 3 2010, 06:42 PM) No problem, thanks should go to SR-71 though who noticed the problem when Vly was in a similar situation.

It's quite odd though of how your ingame resolution changed, normally you can only change it in fullscreen mode and I thought the default was 800 x 600.
It can also be changed, if you launch with "Safe Mode" option selected in ASGS. It then displays gfx settings window prior to launching Allegiance.exe.
Image
Image
WyldKarde
Posts: 229
Joined: Thu Feb 24, 2005 8:00 am
Location: 127.0.0.1

Post by WyldKarde »

ogorass wrote:QUOTE (ogorass @ Jun 3 2010, 06:57 PM) It can also be changed, if you launch with "Safe Mode" option selected in ASGS. It then displays gfx settings window prior to launching Allegiance.exe.
Except for some reason that didn't work for me. :huh:

Edit: To clarify, running in Safe Mode brought up the gfx dialogue, but I still faced crashes when joining a game in fullscreen, or joining windowed then going to fullscreen.
Last edited by WyldKarde on Thu Jun 03, 2010 6:49 pm, edited 1 time in total.
--WK
Image
Post Reply