The A2A Simulations Community

To avoid problems and save setup time, you should read and implement the BOBII Version 2.12 Release Notes that effect your PC environment.

Note1: this update will bring *any* previous version up to 2.12. You do not need any previous patches at all.
Note2: You will need the latest DirectX to run 2.12.
You will get a missing .dll error if you do not. When you run the 2.12 self-installer it will point you to the Microsoft DirectX update page. Update to DirectX9.0c (June version). Unfortunately, there are multiple versions of 9.0c so if in any doubt, update.
Note3: The MultiSkin patch should go ON TOP OF Battle of Britain 2: Wings of Victory v2.12 Patch (English) OR Battle of Britain 2: Wings of Victory v2.12 Patch (International)
You should have a 256M gfx card to be sure to run without issues.
Note4: How to back up your existing settings from earlier BoBII updates.
Buddye's installation guide HERE-> http://www.a2asimulations.com/forum/vie ... 0&t=19368B
Back up your Bdg.txt and \savegame, \2dGauge, and \keyboard folders (these folders contain all your settings and joystick buttons)
Note5: If you have a low end system and experience a crash once into 3D, go to your bdg.txt file and set LANDSCAPE_TEXTURE_SIZE = 1024 (the default is 2048). This will reduce the landscape texture resolution by a factor of 4 and should help users with low system memory.
Note6: The minimum requirements for BoBII have changed very significantly since initial release. To run 2.12 successfully we recommend Win XP/7, 2GB RAM, 1GB Video card, Strong Dual or Quad Core processor.
Note7: Vista and Windows 7 users may need to apply the 'Vista/Windows 7 fix' to your desktop shortcut as a fresh 2.11 install will overwrite the previous shortcut.
Right click on shortcut and go to properties. Go to the compatibility tab. Check "disable desktop composition" and check the privilege level, run this program as an administrator.
Note8: Forcing VSync with ATI card
There is a known issue with the latest ATI cards and VSync. See http://www.a2asimulations.com/forum/vie ... 10&t=21660
In short, you need to right click your ATI tray icon and enable through that (Wait for vertical refresh->Always on).
Note9: Framerates over densely populated areas of 3D objects.
See the section later in this thread. Object rendering is not as efficient as we hope to make it in the future. Be prepared to check your Ground Object Density settings in densely populated urban areas. See below.
Note10: You will not be able to run old campaigns with 2.12. You will need to restart them.
Note11: To run 2.12 with max settings you will need minimum of 3G RAM (ideally 4G). Players with 32 bit Windows7 will need to enable the "/3GB switch" to their system.
viewtopic.php?f=17&t=33282
Note12: To see in-menu videos with Win7, see here: viewtopic.php?p=161307#p161307 or install codecs here: http://www.free-codecs.com/download/indeo_codec.htm
Note13: If you have a wide screen monitor then you must do the folling:
http://www.a2asimulations.com/forum/vie ... 17&t=12695

_________________
Buddye

Intel I7 920 processor (2.66GHz, 8MB cache), 6GB DDR3 Triple Channel @1333MHz, 1.8GB NVIDIA GeForce GTX 295, Sound Blaster X-Fi PCI Sound Card, Windows 7 Home Premium 64 Bit , CH Fighter Stick & Pedals ,TrackIR4 Pro thanks to BobII crew.

Greetings Buddye,
Just installed the update v. 2.12, and unfortunately I had my first crash. I believe it might be video related as 2.10 and 2.11 ran perfectly. Here's the screen message I received "Vertex Buffer Creation Failure".
Could you advise.
System :
2.66 Ghtz Quad core..on an Asus Striker MB
N vidia GTX 260 1 mb mem
4 gig mem

Thanks for any info
David C (Harvey)

The CTD you had is an old and very rare one which I have found no fix as yet.

I ensure I am not guessing incorrectly, please post your PC specs and your crashlog for me to review. The crashlog can be found in your BOBII folder in the crashlog.txt file. Cut and paste the first 20 lines for me to review in this thraed,

_________________
Buddye

Intel I7 920 processor (2.66GHz, 8MB cache), 6GB DDR3 Triple Channel @1333MHz, 1.8GB NVIDIA GeForce GTX 295, Sound Blaster X-Fi PCI Sound Card, Windows 7 Home Premium 64 Bit , CH Fighter Stick & Pedals ,TrackIR4 Pro thanks to BobII crew.

I believe this is the correct file, hope so but the date is a bit confusing mentions May4th 2010...not sure if that refers to the date the crash happened, which was yesterday... I will leave it with you.

------------ Begin of section written with bob.exe, Build/Rebuild all date: May 4 2010 14:53:09 ---------------------------
Bob.exe caused a EXCEPTION_ACCESS_VIOLATION in module ntdll.dll at 001B:7C919AF2, RtlpWaitForCriticalSection()+91 byte(s)
Exception handler called in drawloop.
Write to location 00000010 caused an access violation.
Code: ff 40 10 8b 45 fc 83 e0 01 89 45 e8 8b 06 ff 40
Stack dump:
Stack: 001B:7C919AF2 (0x00D0B404 0x00589610 0x02D0B404 0x00792FE0) ntdll.dll, RtlpWaitForCriticalSection()+91 byte(s)
Stack: 001B:7C901046 (0x00000000 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlEnterCriticalSection()+70 byte(s)

Stack dump (old format):
Exception encountered during stack dump (old format).
EAX=00000000 EBX=00000000 ECX=000004B8 EDX=02D0B414 ESI=02D0B404
EDI=00000000 EBP=00000800 ESP=00000808 EIP=00000000 FLG=00010246
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
Error occurred at 11/8/2011 01:08:16.
C:\Battle of Britain II\Bob.exe, run by Dave Christian.
4 processor(s), type 586.
2048 MBytes physical memory.
OS: 5.1 build 2600 platform 2 Service Pack 3

PS should I erase the txt in the crashlog file now and so it will write a new one ?

You can leave the crashlog file as is for now. BOBII will write a new crashlog file at the end. When ready and all the files are either old releases of BOBII or you have posted the file for us to review, you can just delete the crashlog.txt file from you BOBII folder and BOBII will write a new crashlog.txt file if/when needed.

Your crashlog file date you posted is May 4 2010 which is an old crashlog file. The date in the crashlog file is the specific date that I did the buld for a new version of BOBII.

The 2.12 date is Dec 21, 2012. Look at the last file in your crashlog.txt file and post the first 20 lines for me.

_________________
Buddye

Intel I7 920 processor (2.66GHz, 8MB cache), 6GB DDR3 Triple Channel @1333MHz, 1.8GB NVIDIA GeForce GTX 295, Sound Blaster X-Fi PCI Sound Card, Windows 7 Home Premium 64 Bit , CH Fighter Stick & Pedals ,TrackIR4 Pro thanks to BobII crew.

Ok Here goes again. BTW I was reading alot last night and came across the ref to use "LARGE ADDRESS" utility program.
Downloaded it last night and installed. Have run BOB11 today with the Historic scenario LONDON raid..where there are literally
over 100 aircraft...and not a shimmer or hint of a problem...Will keep trying. I believe the scenario that caused this original crash was the Portsmouth flight. Here are the last 20 lines of the crash log as of today.

C:\WINDOWS\system32\GDI32.dll, loaded at 0x77f10000 - 286720 bytes - 49006fbe - file date is 10/23/2008 05:36:14
C:\WINDOWS\system32\SHLWAPI.dll, loaded at 0x77f60000 - 474112 bytes - 4b1e1b10 - file date is 12/8/2009 02:23:28
C:\WINDOWS\system32\Secur32.dll, loaded at 0x77fe0000 - 56832 bytes - 4a433476 - file date is 6/25/2009 01:25:26
C:\WINDOWS\system32\urlmon.dll, loaded at 0x78130000 - 1212416 bytes - 50926872 - file date is 11/1/2012 05:17:54
C:\Program Files\Common Files\Ahead\DSFilter\MSVCR71.dll, loaded at 0x7c340000 - 348160 bytes - 3e561eac - file date is 2/21/2003 14:42:22
C:\Program Files\Common Files\Ahead\DSFilter\MSVCP71.dll, loaded at 0x7c3a0000 - 499712 bytes - 3e77eebb - file date is 3/19/2003 06:14:52
C:\WINDOWS\system32\kernel32.dll, loaded at 0x7c800000 - 990208 bytes - 506bc5e5 - file date is 10/2/2012 21:58:14
C:\WINDOWS\system32\ntdll.dll, loaded at 0x7c900000 - 718336 bytes - 4d00f27d - file date is 12/9/2010 08:15:10
C:\WINDOWS\system32\SHELL32.dll, loaded at 0x7c9c0000 - 8462848 bytes - 4fd20b8c - file date is 6/8/2012 07:26:20
C:\WINDOWS\system32\oledlg.dll, loaded at 0x7df70000 - 122880 bytes - 4802a117 - file date is 4/13/2008 17:12:02
C:\WINDOWS\system32\USER32.dll, loaded at 0x7e410000 - 578560 bytes - 4802a11b - file date is 4/13/2008 17:12:08

------------ End of section written with bob.exe, Build/Rebuild all date: May 4 2010 14:53:09 ---------------------------

Sorry Buddye, I'll try again, this time its the 1st 20 lines of the last file in the crashlog

Module list: names, addresses, sizes, time stamps and file times:
C:\WINDOWS\system32\Normaliz.dll, loaded at 0x00340000 - 23552 bytes - 44a3ec46 - file date is 1/7/2009 19:20:36
C:\WINDOWS\system32\guard32.dll, loaded at 0x00370000 - 301264 bytes - 509ad88a - file date is 11/7/2012 16:37:36
C:\Battle of Britain II\Bob.exe, loaded at 0x00400000 - 4411392 bytes - 4be978f6 - file date is 5/11/2010 11:34:18
C:\WINDOWS\system32\d3dx9_30.dll, loaded at 0x04020000 - 2388176 bytes - 442d83c4 - file date is 3/31/2006 13:40:58
C:\Program Files\NVIDIA Corporation\nView\nview.dll, loaded at 0x04ee0000 - 1564008 bytes - 503f0aca - file date is 2/9/2013 20:20:28
C:\WINDOWS\system32\dbghelp.dll, loaded at 0x051a0000 - 640000 bytes - 4802a0b2 - file date is 4/13/2008 17:11:52
C:\WINDOWS\system32\nvwddi.dll, loaded at 0x06350000 - 54272 bytes - 5116d5da - file date is 2/9/2013 17:27:32
C:\Battle of Britain II\English\text\boblang.dll, loaded at 0x07040000 - 679936 bytes - 437b62b2 - file date is 11/13/2007 14:40:50
C:\Program Files\AltoMP3 Gold\Filters\MpaSplitter.ax, loaded at 0x078e0000 - 352256 bytes - 451f3e67 - file date is 9/30/2006 21:04:56
C:\Program Files\Common Files\Ahead\DSFilter\NeFLVSplitter.ax, loaded at 0x07f10000 - 136488 bytes - 467fb59a - file date is 2/12/2008 11:41:52
C:\Program Files\AltoMP3 Gold\Filters\MP4Splitter.ax, loaded at 0x07f30000 - 499712 bytes - 451f3932 - file date is 9/30/2006 20:42:42
C:\Battle of Britain II\muParser.dll, loaded at 0x10000000 - 225280 bytes - 428e0f2d - file date is 11/13/2007 19:25:56
C:\PROGRA~1\COMMON~1\merlin\ocx\Rbutton.ocx, loaded at 0x10100000 - 401408 bytes - 45ab6c8c - file date is 1/15/2007 08:59:10
C:\PROGRA~1\COMMON~1\merlin\ocx\RListBox.ocx, loaded at 0x10600000 - 503808 bytes - 45ab6cda - file date is 1/15/2007 09:00:28
C:\PROGRA~1\COMMON~1\merlin\ocx\Rscrlbar.ocx, loaded at 0x10700000 - 376832 bytes - 45ab6d00 - file date is 1/15/2007 09:01:06
C:\WINDOWS\system32\WININET.dll, loaded at 0x3d930000 - 916992 bytes - 50926872 - file date is 11/1/2012 05:17:54

You want the lines which start from

------------ Begin of section written with bob.exe,....

and following. The date on that line is the date of the build. May 4,2012 is patch v2.11
The date the crash is written is found in the listing between the stack dump and the
loaded modules. In the first crashlog you posted it is here:

Error occurred at 11/8/2011 01:08:16.

So that log is 1 1/2 years old.

I do apologise, but thats all that is there right now. My only thought would be that the crash I experienced with the message "Vertex Buffer Creation failure" didnt write to the crashlog file for some reason.??
I have looked right through the entire log and there are no ver files that the exe wrote using v2.12 exe..so
I will attempt to replicate and see if anything writes to the crashlog file. I have cleared the file out so no more references to 2010 are there, and any new crashes will be the only ones there if i can get the same error to happen.
Thanks so much for all your time will be in contact soon
David C (Harvey)

Hi Guys
I have been successfully running V2.11 with skins & it was great! I have just downloaded &
installed v12 but it starts up ok then after 10/20 secs crashes with a note 'Battle of Britain English Text has stopped
working'
Can you advise me what to do/what I have done wrong plz

Hi MM, I'll copy your question to a new thread in this
forum, and answer it there (don't want to clutter the
sticky). Here:
viewtopic.php?f=17&t=38834

Thanks

Hi All,

I have fixed the crash error:-
battle of britain english text has stopped working

Symptom I was having, crashing while playing for few minutes.

I am using W7 64bit, on desktop right click and choose Personalize, then click on Display, then on Set custom text size (DPI)
and uncheck:- Use Windows XP style DPI scaling.

The above took me awhile to figure out, I persisted with it, changing Option settings in the game made no difference

Sorry, Battle of Britain English Text is the identifier for the program,
and all and any crash appears under that name which occurred while
the program has focus, whether due to the program itself, or "modules"
which are actually parts of windows, such as ntdll.dll and d3dx9.dll

To identify a specific crash, you need the crashlog, and note the
initial lines after the start of the last appended report, which will look
like (I just grabbed the first example I could find in the forum here):


The date on the top line tells me it's the release version of v2.12;
the "module bob.exe" tells me it was an actual BoB crash, rather than
a windows ntdll.dll d3dx9.dll or other (there are several) windows
module crash.

The actual crash type itself is identified by the 0023:00605335, COverlay::DecisionMessage()+81 byte(s)
which give the specific bob.exe module, and point within it which
triggered the problem.

Not that this helps me much, as I'm not a coder. However, I can tell from
this that the crash is a legitimate bob problem, of some sort. However, it
may still be due to issues with the machine configuration. I don't know.

Anyway, if you could find the crashlog entry (in crashlog.txt, in the
<bobroot> folder - the one with the program exe in it) and post that information,
that could potentially be helpful in identifying this crash for other users.

Can anyoone help with my game crashing as soon as I click frag or fly please.

Problem signature:
Problem Event Name: BEX
Application Name: bob.exe
Application Version: 2.1.1.0
Application Timestamp: 4be978f6
Fault Module Name: bob.exe
Fault Module Version: 2.1.1.0
Fault Module Timestamp: 4be978f6
Exception Offset: 00075489
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: e052
Additional Information 2: e052e5e252fdaea82b4649daee7d819d
Additional Information 3: ffb0
Additional Information 4: ffb0e06c6a20e7aba8cbacfb75b457c5