Yet another newbie question

new reply
Trader1
Airman Basic
Posts: 6
Joined: 15 Aug 2013, 12:59

Yet another newbie question

Post by Trader1 »

Hi Guys,
I have been researching combat flight sims for a while and I am nearly ready to pull the trigger on BobII. Before I do, I have yet another p.i.t.a. newbie question about the Direct x 9 requirement. I have already downloaded and extracted all of the d3dx9 dll's from 24 thru 43. After reading some of the posts, I had intended on manually copying them into my \system32\ folder. However, in the course of my research online, I found some mention of "registering" dll's using something called "Regsvr32". I am assuming that this registering is something that would normally be done during a typical direct x install. Since I haven't seen any mention of registering the dll's needed for BobII either in the forum or on this site: http://www.m3fe.com/760 that has been referenced in several posts, can I assume that if I manually copy the dll's into the system32 folder that BobII will see them and run properly? FYI, I'm running Win7 64 bit and the dll's I extracted were the 64 bit versions, not the 32 bit ones. I apologize for another DX9 question, I just want to get this right prior to my purchase, and avoid any OS problems.
Thanks

User avatar
Buddye
BDG
Posts: 12465
Joined: 30 Jul 2005, 12:59
Location: South East Texas, USA

Re: Yet another newbie question

Post by Buddye »

I do not understand your question. If you download and install the latest DirectX 9c then all should be OK.

You will need the latest DirectX to run 2.12 or any new version of BOBII. Even if you have a new PC you will need to update to the latest DirectX 9C. We have had many players trying to run BOBII without the latest DirectX and having CTD problems.

The easiest way to update DirectX is when you run the 2.12 (or the latest) self-installer and the self-installer will point you to the Microsoft update page. Just go ahead and update your DirectX to the latest version.

For all of those who forget or did not update their DirectX and get the missing dll, just re-run the self-installer and update the DirectX when it points you to the Microsoft web page.

It is a Web installer and only updates what is needed. Here is a link to the DirectX web installer:

http://www.microsoft.com/downloads/deta ... laylang=en

The key question you need to consider is , "will my PC run BOBII effectively?" Here is a link to help you:

http://a2asimulations.com/forum/viewtop ... 17&t=10091
Buddye

Intel I7 920 4 core 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

User avatar
PV
BDG
Posts: 5188
Joined: 13 Nov 2004, 08:21
Location: Lost in the tundra, Canada

Re: Yet another newbie question

Post by PV »

Trader1, I manually copied the dlls from 24 to about 40, as they came available,
with no other action, and it worked fine. Since then I got a new machine and
did the full update from the web installer. I have no idea if there are any other
lurking bits for DX9.1c which the manual process misses, but I know it didn't affect
the operation of BoB2. However, doing the web installer update is quite painless,
and then you'll be sure you aren't missing anything which might be needed for
something else.

Trader1
Airman Basic
Posts: 6
Joined: 15 Aug 2013, 12:59

Re: Yet another newbie question

Post by Trader1 »

Thanks to both of you. I apologize for not being clear with my question. It really boiled down to just copying the dll's into the folder as opposed to using the web installer. PV, your method was what I was going to use. Glad to know it works.
Just as an aside, I have never been a game player, particularly on my PCs. I use them for other, much more serious, work and can ill afford crashes, OS reinstalls, etc. that seem to be part and parcel of typical gaming installs, based on what I've read online. I keep a very cautious, even paranoid viewpoint when it comes to any new software install, a sort of variation on the "if it ain't broke, don't fix it" theme. That's why I, and in my estimation many other Bob2 newbies, ask so many questions about the dx9 issue.
I know you probably get frustrated with the same question being asked over and over again, and I apologize for asking it yet again, but I hope you understand (not necessarily agree with) my point of view.
As I said in my first post, I had been looking at various other flight sims/games for a while, and I decided against them because of various install issues that I didn't like, including one online sim that would have installed bit torrent "seeding" on my machine. When I found Bob2 (almost by accident), it looked like the "safest" sim to install. And in reading posts by the BDG members, I appreciated the passion you have for Bob2.
So thanks again and, once I do some training, maybe I'll see you in the sky.

User avatar
Lewis - A2A
A2A Lieutenant Colonel
Posts: 33284
Joined: 06 Nov 2004, 23:22
Location: Norfolk UK
Contact:

Re: Yet another newbie question

Post by Lewis - A2A »

I would say that as a gamer I've never ever had to reinstall an OS and also as a PC tech I can tell you, you would have to really really go mental on an install to get to that point. ...And I mean washing ur PC I the kitchen sink mental to get to that point.

Best and safest way is to use the web installer from Microsoft. As soon as you start manually doing/tryng to do things unless your a software engineer or tech then its actually more likely to really screw a system and cause instability.

Since working for A2A I've pretty much stopped all tweaking in order to have a stable game and work system.




Sent from my iPhone using Tapatalk
A2A Facebook for news live to your social media newsfeed
A2A Youtube because a video can say a thousand screenshots,..
A2A Simulations Twitter for news live to your social media newsfeed
A2A Simulations Community Discord for voice/text chat

Trader1
Airman Basic
Posts: 6
Joined: 15 Aug 2013, 12:59

Re: Yet another newbie question

Post by Trader1 »

Gentlemen,
I thought you might be interested in my installation experience. I will attempt to be clearer with this post than in my initial one at the beginning of this thread. I apologize for the length, but maybe the info will be useful.

I Installed BobII v2.06 after downloading from A2A. Received 2 errors on startup - Error 1- The program can't start because d3dx9_31.dll is missing from your computer. Error 2- The application was unable to start correctly (0xc000007b). These two errors were as a result of the different locations into which I had copied the x64 versions of the d3dx9 dlls on my system. Error 1 was when the x64 bit dlls were located in the system32 folder. Error 2 was when I moved them into the Bob2 install folder. I'll explain why I did that later.

Decided to install the v2.12 update anyway, figuring it couldn't get any worse. Error #1 (with the dlls in the system32 folder) was repeated, but with the system looking for d3dx9_30.dll, instead of 31. Error #2 (with the dlls in the Bob2 install folder) was exactly the same as error 2 above.

I had been working on a theory about the dlls prior to installing BobII. It started with the fact that PV (and apparently many others) had been able to copy the dlls (as opposed to using the web installer to install them) with no ill effects on BobII. It also seemed that copying the dlls is common in the game community, witness this forum's multiple references to this site: http://www.m3fe.com/760. Doing a bit of snooping online, I found this Microsoft page: http://support.microsoft.com/kb/910813. The page is titled "Game Error: The file d3dx9_xx.DLL was not found". The first recommended method is, of course, installing the latest version of DirectX. However, if you scroll down about halfway, you'll find the 2nd recommended method, which is, and I quote: "Manually copy the file. To resolve this issue, copy the D3dx9_25.dll file or the D3dx9_27.dll file from the disc 1 CD/DVD of the game CD/DVD pack to the corresponding game folder." The dlls used in the quote are just their examples. Now things were beginning to get a bit clearer. Remember, I hadn't yet installed BobII. I did a search of both my hard drives for "d3dx9". I expected to find nothing, because I had never installed anything other than DirectX 11 during the initial build of my system. Surprisingly, I found d3dx9_43.dll, located in my mail client folder, Thunderbird. No other d3dx9 files were found. That confirmed several things for me: 1) These dlls are not OS requirements, they're application specific. 2) The old DOS/Win3.0 methods of file location are not totally gone in Windows 7. 3) This old 50 something brain still has a few nodes left that are firing.

There was just one question left: Why, when I placed the dlls in the BobII program folder, didn't it fire up? The answer was fairly simple. It's an old program. It wants the old versions. As soon as I extracted the 32 bit versions of d3dx9_30.dll and d3dx9_31.dll and placed them in the BobII program folder, BobII was happy and I was crashing planes all over the place. Remember, newbie flyer here.

I spent most of one day configuring and tweaking the video and flying practice flights with absolutely no problems whatsoever. Admittedly, I haven't poked into every nook and cranny of BobII, so maybe the jury is still out on my solution, but as far as my current experience goes, copying the 32 bit versions of those two dlls into the BobII program folder is enough to satisfy BobII. Since I don't have any other games (don't have the patience for them) on this system, your requirements may be very different.

Anyway, just thought you might be interested.

By the way, here is my system configuration info (please remember that gaming is not a primary function for this machine):
I built this system near the end of 2010.
ASUS M4A88TD-V EVO/USB3 AMD 880G mb
AMD Phenom II X4 555 Black Edition 3.2ghz Quad Core processor
Corsair XMS3 8gb ddr3 1333 sdram
HIS Radeon HD 6670 pcie 2.1 1gb ddr5 video card
Viewsonic VX2250WM 21.5" led monitor
Thrustmaster T16000m (just purchased. first joystick I've owned)
Windows 7 home premium 64 bit os
AMD Catalyst display driver v.13.4 (5/29/13)
Direct X 11 (installed during os install), no other Direct X versions installed.

Trader1
Airman Basic
Posts: 6
Joined: 15 Aug 2013, 12:59

Re: Yet another newbie question

Post by Trader1 »

And of course after all of the above, I got my first crash (just flying a training flight). Here's the log:

------------ Begin of section written with bob.exe, Build/Rebuild all date: Dec 21 2012 17:39:32 ---------------------------
Bob.exe caused a EXCEPTION_ACCESS_VIOLATION in module Bob.exe at 0023:0040EBE3, CMIGApp::Run()+189 byte(s), c:\merlin\bob\src\mfc\mig.cpp, line 1943+5 byte(s)
Exception handler called in int CMIGApp::Run().
Read from location 00000000 caused an access violation.
Code: 8b 08 50 ff 51 0c 3d 69 08 76 88 74 0a 6a 64 ff
Stack dump:
Stack: 0023:0040EBE3 (0x00001DB1 0x00000002 0x00000001 0x0047A825) Bob.exe, CMIGApp::Run()+189 byte(s), c:\merlin\bob\src\mfc\mig.cpp, line 1943+5 byte(s)
Stack: 0023:0068F121 (0x00400000 0x00000000 0x063C1FF3 0x00000001) Bob.exe, AfxWinMain()+104 byte(s), f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\winmain.cpp, line 47+7 byte(s)
Stack: 0023:0047A825 (0xFFFDE000 0x0018FFD4 0x76EF9F72 0xFFFDE000) Bob.exe, __tmainCRTStartup()+375 byte(s), f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c, line 324+28 byte(s)
Stack: 0023:74F933AA (0xFFFDE000 0x765B8F9D 0x00000000 0x00000000) kernel32.dll, BaseThreadInitThunk()+18 byte(s)
Stack: 0023:76EF9F72 (0x0047A88E 0xFFFDE000 0x00000000 0x00000000) ntdll.dll, RtlInitializeExceptionChain()+99 byte(s)
Stack: 0023:76EF9F45 (0x0047A88E 0xFFFDE000 0x00000000 0x78746341) ntdll.dll, RtlInitializeExceptionChain()+54 byte(s)

Stack dump (old format):
0018ffdc: 0047a88e fffde000 00000000 00000000 00000000 00000000 0047a88e fffde000
0018fffc: 00000000

EAX=00000000 EBX=00000001 ECX=74B8371A EDX=000000B7 ESI=76970B4A
EDI=007A00E0 EBP=0018FFEC ESP=0018FFDC EIP=76EF9F45 FLG=00210246
CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B
Error occurred at 8/20/2013 17:03:52.
E:\HB Program Files\Battle of Britain II\Bob.exe, run by HB2.
4 processor(s), type 586.
0 MBytes physical memory.
OS: 6.1 build 7601 platform 2 Service Pack 1

Module list: names, addresses, sizes, time stamps and file times:
E:\HB Program Files\Battle of Britain II\Bob.exe, loaded at 0x00400000 - 4464640 bytes - 50d4f336 - file date is 1/2/2013 14:33:50
E:\HB Program Files\Battle of Britain II\d3dx9_30.dll, loaded at 0x064c0000 - 2388176 bytes - 442d83c4 - file date is 3/31/2006 12:40:58
E:\HB Program Files\Battle of Britain II\English\text\boblang.dll, loaded at 0x0cb30000 - 679936 bytes - 437b62b2 - file date is 11/13/2007 13:40:50
E:\HB Program Files\Battle of Britain II\muParser.dll, loaded at 0x10000000 - 225280 bytes - 428e0f2d - file date is 11/13/2007 18:25:56
C:\PROGRA~2\COMMON~1\merlin\ocx\Rbutton.ocx, loaded at 0x10100000 - 401408 bytes - 45ab6c8c - file date is 1/15/2007 07:59:10
C:\PROGRA~2\COMMON~1\merlin\ocx\Redit.ocx, loaded at 0x10300000 - 393216 bytes - 45ab6ca9 - file date is 1/15/2007 07:59:38
C:\PROGRA~2\COMMON~1\merlin\ocx\RListBox.ocx, loaded at 0x10600000 - 503808 bytes - 45ab6cda - file date is 1/15/2007 08:00:28
C:\PROGRA~2\COMMON~1\merlin\ocx\Rscrlbar.ocx, loaded at 0x10700000 - 376832 bytes - 45ab6d00 - file date is 1/15/2007 08:01:06
C:\PROGRA~2\COMMON~1\merlin\ocx\RStatic.ocx, loaded at 0x10a00000 - 385024 bytes - 45ab6d4c - file date is 1/15/2007 08:02:22
C:\Windows\SysWOW64\MFPlat.DLL, loaded at 0x6eb10000 - 352768 bytes - 4a5bda38 - file date is 7/13/2009 21:15:40
C:\Windows\system32\dbghelp.dll, loaded at 0x6ec10000 - 854016 bytes - 4ce7b7bc - file date is 11/20/2010 08:18:28
C:\Windows\system32\D3DIM700.DLL, loaded at 0x6ed00000 - 817664 bytes - 4a5bd9ab - file date is 7/13/2009 21:15:10
C:\Windows\system32\DCIMAN32.dll, loaded at 0x6edd0000 - 10240 bytes - 4a5bd9b4 - file date is 7/13/2009 21:15:10
C:\Windows\system32\DDRAW.dll, loaded at 0x6ede0000 - 531968 bytes - 4a5bd9b8 - file date is 7/13/2009 21:15:12
C:\Windows\SysWOW64\devenum.dll, loaded at 0x6ef60000 - 66560 bytes - 4a5bd9be - file date is 7/13/2009 21:15:12
C:\Windows\SysWOW64\quartz.dll, loaded at 0x6ef80000 - 1328128 bytes - 4ea78b37 - file date is 10/26/2011 00:32:12
C:\Windows\system32\HID.DLL, loaded at 0x6f100000 - 22016 bytes - 4a5bd9ec - file date is 7/13/2009 21:15:26
C:\Windows\system32\atiumdva.dll, loaded at 0x6f110000 - 4450264 bytes - 5154ed9a - file date is 3/28/2013 22:36:50
C:\Windows\system32\atiumdag.dll, loaded at 0x6f560000 - 5944264 bytes - 5154ef0f - file date is 3/28/2013 22:36:44
C:\Windows\system32\aticfx32.dll, loaded at 0x6fb20000 - 970912 bytes - 5154f765 - file date is 3/28/2013 22:37:00
C:\Windows\system32\midimap.dll, loaded at 0x6fc10000 - 16896 bytes - 4a5bda84 - file date is 7/13/2009 21:15:42
C:\Windows\system32\atiu9pag.dll, loaded at 0x6fc20000 - 92304 bytes - 5154e95f - file date is 3/28/2013 22:37:04
C:\Windows\system32\MSACM32.dll, loaded at 0x6fc40000 - 72192 bytes - 4a5bda4e - file date is 7/13/2009 21:15:44
C:\Windows\system32\msacm32.drv, loaded at 0x6fc60000 - 20992 bytes - 4a5bda4f - file date is 7/13/2009 21:14:10
C:\Windows\system32\AUDIOSES.DLL, loaded at 0x6fc70000 - 195584 bytes - 4ce7b725 - file date is 11/20/2010 08:18:06
C:\Windows\system32\wdmaud.drv, loaded at 0x6fcb0000 - 172032 bytes - 4ce7ba26 - file date is 11/20/2010 08:16:52
C:\Windows\system32\PROPSYS.dll, loaded at 0x6fce0000 - 988160 bytes - 4ce7b983 - file date is 11/20/2010 08:20:58
C:\Windows\system32\MMDevAPI.DLL, loaded at 0x6fde0000 - 213504 bytes - 4ce7b892 - file date is 11/20/2010 08:19:40
C:\Windows\system32\d3d9.dll, loaded at 0x6fe20000 - 1828352 bytes - 4ce7b7b3 - file date is 11/20/2010 08:18:26
C:\Windows\system32\DINPUT8.dll, loaded at 0x6fff0000 - 145408 bytes - 4a5bd9c1 - file date is 7/13/2009 21:15:12
C:\Windows\system32\DSOUND.dll, loaded at 0x70020000 - 453632 bytes - 4a5bd9fd - file date is 7/13/2009 21:15:14
C:\Windows\system32\oledlg.dll, loaded at 0x700a0000 - 103424 bytes - 4a5bdace - file date is 7/13/2009 21:16:14
C:\Windows\system32\rsaenh.dll, loaded at 0x71e90000 - 242936 bytes - 4a5bdae0 - file date is 7/13/2009 21:17:56
C:\Windows\system32\dwmapi.dll, loaded at 0x72100000 - 67072 bytes - 4a5bda07 - file date is 7/13/2009 21:15:14
C:\Windows\system32\WINSPOOL.DRV, loaded at 0x72140000 - 320000 bytes - 4ce7ba4b - file date is 11/20/2010 08:16:52
C:\Windows\system32\CRYPTSP.dll, loaded at 0x72410000 - 78848 bytes - 4a5bda3d - file date is 7/13/2009 21:15:08
C:\Windows\system32\uxtheme.dll, loaded at 0x724e0000 - 245760 bytes - 4a5bdb3c - file date is 7/13/2009 21:11:26
C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll, loaded at 0x72560000 - 530432 bytes - 4ce7b82c - file date is 11/20/2010 08:18:24
C:\Windows\system32\ntmarta.dll, loaded at 0x726e0000 - 121856 bytes - 4a5bdae9 - file date is 7/13/2009 21:16:12
C:\Windows\system32\VERSION.dll, loaded at 0x72720000 - 21504 bytes - 4a5bdb2b - file date is 7/13/2009 21:16:18
C:\Windows\system32\AVRT.dll, loaded at 0x72960000 - 14336 bytes - 4a5bd998 - file date is 7/13/2009 21:15:00
C:\Windows\system32\WINMM.dll, loaded at 0x74060000 - 194048 bytes - 4ce7ba42 - file date is 11/20/2010 08:21:38
C:\Windows\system32\ksuser.dll, loaded at 0x74380000 - 4608 bytes - 4a5bdab3 - file date is 7/13/2009 21:15:36
C:\Windows\system32\d3d8thk.dll, loaded at 0x74650000 - 11264 bytes - 4a5bd9a8 - file date is 7/13/2009 21:15:10
C:\Windows\system32\POWRPROF.dll, loaded at 0x74670000 - 145408 bytes - 4a5bdb0c - file date is 7/13/2009 21:16:14
C:\Windows\syswow64\CRYPTBASE.dll, loaded at 0x74900000 - 36864 bytes - 4a5bbf41 - file date is 7/13/2009 21:15:08
C:\Windows\syswow64\SspiCli.dll, loaded at 0x74910000 - 96768 bytes - 4fc997c1 - file date is 6/2/2012 00:34:10
C:\Windows\syswow64\iertutil.dll, loaded at 0x74970000 - 2048512 bytes - 51f1d8b5 - file date is 7/25/2013 23:12:02
C:\Windows\syswow64\KERNELBASE.dll, loaded at 0x74b70000 - 274944 bytes - 50b83c8a - file date is 11/30/2012 00:54:00
C:\Windows\syswow64\imagehlp.dll, loaded at 0x74bc0000 - 159232 bytes - 4f4f07d3 - file date is 3/1/2012 01:33:24
C:\Windows\syswow64\WINTRUST.dll, loaded at 0x74bf0000 - 175104 bytes - 51db9720 - file date is 7/9/2013 00:52:12
C:\Windows\syswow64\msvcrt.dll, loaded at 0x74c20000 - 690688 bytes - 4eeaf722 - file date is 12/16/2011 03:53:00
C:\Windows\SysWOW64\sechost.dll, loaded at 0x74cd0000 - 92160 bytes - 4a5bdb04 - file date is 7/13/2009 21:16:14
C:\Windows\syswow64\ole32.dll, loaded at 0x74cf0000 - 1414144 bytes - 4ce7b96f - file date is 11/20/2010 08:20:50
C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll, loaded at 0x74e50000 - 4096 bytes - 50f322f9 - file date is 3/13/2013 12:16:06
C:\Windows\syswow64\normaliz.DLL, loaded at 0x74e60000 - 2048 bytes - 4a5bdad4 - file date is 7/13/2009 21:09:02
C:\Windows\syswow64\GDI32.dll, loaded at 0x74e70000 - 311296 bytes - 4ce7ba53 - file date is 11/20/2010 08:08:52
C:\Windows\syswow64\comdlg32.dll, loaded at 0x74f00000 - 485888 bytes - 4ce7b82d - file date is 11/20/2010 08:18:24
C:\Windows\syswow64\kernel32.dll, loaded at 0x74f80000 - 1114112 bytes - 50b83c89 - file date is 11/30/2012 00:54:00
C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll, loaded at 0x75090000 - 3072 bytes - 50f322eb - file date is 3/13/2013 12:16:06
C:\Windows\syswow64\CFGMGR32.dll, loaded at 0x750a0000 - 145920 bytes - 4ddb8851 - file date is 5/24/2011 06:39:40
C:\Windows\syswow64\SETUPAPI.dll, loaded at 0x750d0000 - 1667584 bytes - 4ce7b9d9 - file date is 11/20/2010 08:21:16
C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll, loaded at 0x75280000 - 2560 bytes - 50f3244e - file date is 3/13/2013 12:16:06
C:\Windows\system32\IMM32.DLL, loaded at 0x75290000 - 119808 bytes - 4ce7ba53 - file date is 11/20/2010 08:08:52
C:\Windows\syswow64\ADVAPI32.dll, loaded at 0x752f0000 - 640512 bytes - 4ce7b706 - file date is 11/20/2010 08:18:04
C:\Windows\syswow64\SHELL32.dll, loaded at 0x75390000 - 12872704 bytes - 512d91aa - file date is 2/27/2013 00:55:06
C:\Windows\syswow64\SHLWAPI.dll, loaded at 0x75fe0000 - 350208 bytes - 4ce7b9e2 - file date is 11/20/2010 08:21:20
C:\Windows\syswow64\OLEAUT32.dll, loaded at 0x76040000 - 571904 bytes - 4e58702a - file date is 8/27/2011 00:26:28
C:\Windows\syswow64\RPCRT4.dll, loaded at 0x760d0000 - 663552 bytes - 51db9710 - file date is 7/9/2013 00:52:34
C:\Windows\syswow64\USP10.dll, loaded at 0x762f0000 - 626688 bytes - 50adaddf - file date is 11/22/2012 00:45:04
C:\Windows\syswow64\CLBCatQ.DLL, loaded at 0x76390000 - 522240 bytes - 4a5bd9b1 - file date is 7/13/2009 21:15:04
C:\Windows\syswow64\MSCTF.dll, loaded at 0x76420000 - 828928 bytes - 4a5bda69 - file date is 7/13/2009 21:15:44
C:\Windows\syswow64\NSI.dll, loaded at 0x764f0000 - 8704 bytes - 4a5bdad9 - file date is 7/13/2009 21:16:12
C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll, loaded at 0x76500000 - 9728 bytes - 50f3244f - file date is 3/13/2013 12:16:06
C:\Windows\syswow64\WININET.dll, loaded at 0x76510000 - 1767936 bytes - 51f1c6a2 - file date is 7/25/2013 23:13:26
C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll, loaded at 0x766d0000 - 10752 bytes - 50f3243a - file date is 3/13/2013 12:16:06
C:\Windows\syswow64\CRYPT32.dll, loaded at 0x766e0000 - 1166848 bytes - 51db9640 - file date is 7/9/2013 00:46:32
C:\Windows\syswow64\PSAPI.DLL, loaded at 0x76800000 - 6144 bytes - 4a5bdace - file date is 7/13/2009 21:16:14
C:\Windows\syswow64\MSASN1.dll, loaded at 0x76870000 - 34304 bytes - 4ce7b8c9 - file date is 11/20/2010 08:19:46
C:\Windows\syswow64\WS2_32.dll, loaded at 0x76910000 - 206848 bytes - 4ce7ba68 - file date is 11/20/2010 08:21:40
C:\Windows\syswow64\USER32.dll, loaded at 0x76950000 - 833024 bytes - 4ce7ba59 - file date is 11/20/2010 08:08:58
C:\Windows\syswow64\WLDAP32.dll, loaded at 0x76a50000 - 269824 bytes - 4ce7ba62 - file date is 11/20/2010 08:21:38
C:\Windows\syswow64\DEVOBJ.dll, loaded at 0x76aa0000 - 64512 bytes - 4ddb887d - file date is 5/24/2011 06:40:06
C:\Windows\syswow64\LPK.dll, loaded at 0x76e90000 - 25600 bytes - 4a5bdb3b - file date is 7/13/2009 21:11:24
C:\Windows\SysWOW64\ntdll.dll, loaded at 0x76ec0000 - 1292192 bytes - 51db9710 - file date is 7/9/2013 00:53:48

------------ End of section written with bob.exe, Build/Rebuild all date: Dec 21 2012 17:39:32 ---------------------------

User avatar
Buddye
BDG
Posts: 12465
Joined: 30 Jul 2005, 12:59
Location: South East Texas, USA

Re: Yet another newbie question

Post by Buddye »

Check and double check the following release notes from our 2.12 Update release. Focus on Note 2, Note 7, and Note 13.

*********************************************************************************************************************************************************************************[/b]

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.
Note12: To see in-menu videos with Win7, see here: http://a2asimulations.com/forum/viewtop ... 07#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 following:
http://www.a2asimulations.com/forum/vie ... 17&t=12695
*********************************************************************************************************************************************************************************
Buddye

Intel I7 920 4 core 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

Trader1
Airman Basic
Posts: 6
Joined: 15 Aug 2013, 12:59

Re: Yet another newbie question

Post by Trader1 »

Thanks, Buddye
Note 1 - Went directly from 2.06 to 2.12 (see post at 2:29pm above).
Note 2 - Not getting missing dll error (see post at 2:29pm above).
Note 3 - Have not installed Multiskin
Note 4 - Does not apply to this install.
Note 5 - May try this if I have further crashes, but my system is hardly low end.
Note 6 - My system meets or exceeds these requirements (see post at 2:29pm above).
Note 7 - run as admin is already checked, disable desktop composition was not, is now.
Note 8 - no Vsync issues
Note 9 - Already adjusted density settings. Not a problem
Note 10 - Not applicable
Note 11 - Not applicable (see system info in post at 2:29pm above)
Note 12 - Not an issue
Note 13 - Already did that during tweaking as mentioned in post at 2:29pm .
I'm not looking for a solution to the crash, just thought you, Pv or Lewis might be interested in the log.

User avatar
Buddye
BDG
Posts: 12465
Joined: 30 Jul 2005, 12:59
Location: South East Texas, USA

Re: Yet another newbie question

Post by Buddye »

The crash was strange so I am concerned that the set-up was OK.

Is the game running OK? Can you complete some Instant Action missions?

Did you hit any strange keys (like alt+tab)? Did you get an error message(like lost device)?

Your answer "Note 2 - Not getting missing dll error (see post at 2:29pm above", does not mean that you have installed the latest DirectX 9c. Most DirectX9c issues are strange CTD like the one you had.
Buddye

Intel I7 920 4 core 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

Trader1
Airman Basic
Posts: 6
Joined: 15 Aug 2013, 12:59

Re: Yet another newbie question

Post by Trader1 »

My personal belief is that the crash was an anomaly, caused by a rookie pilot (me). I have indeed run many "takeoff" training flights, and in fact managed to land back at the original airfield when running the sim last night. First time for that. Not being a pilot, I've been having a lot of trouble with orientation and lining up approaches to the runway. I spend a lot of time flying around just looking for the airfield. Beginning to make use of the heading reading on the screen.

As for the crash, I got "froggy" once and decided to try an air combat training flight (that was a mistake) and lost control of just about everything. It is quite likely that I hit a bad key combination in the confusion. I remember thinking at the time "what did I just hit? (on the keyboard). There was an error message, but I'm sorry I can't remember it exactly. I do remember thinking "well, the OS really doesn't like what I just did", but there was no "lost device" error. My impression was a software/OS issue. It just stopped and partially blacked out the screen and the message said BobII would not continue and it kicked me out to Windows desktop.

Subsequent to that event, I flew several more takeoff training flights, since it's obvious that's all I'm qualified for, with no incident. Tweaked the video a bit more and I'm getting very smooth performance out of the system.

In short, as my dad used to say "It's cockpit trouble, son". I'll let you know if I crash again (not the planes, just the sim).

new reply

Return to “BOB2 Technical Support”

Who is online

Users browsing this forum: No registered users and 6 guests