Hi,

Having a dual graphics laptop ( integrated Intel + Nvidia GT540 M),BOB WoV is the only game that I cannot force to run with the Nvidia GC: although the bob.exe and the videogame.exe are set with the Nvidia card on the Nvidia control panel, the BoB graphic options does not give me other choices than the Intel integrated grahics...

Any hint ?

Thank you in advance !

Don't know; my laptop has a dual graphics that
uses two ATI chips - I just open the ATI vidcard
window and select which programs should use the
enhanced chip. Inside BoB2 there's nothing to select,
as it only sees one option for display, at the
laptop default resolution and clock.

...I presume you have the "Use Desktop Resolution"
option set to OFF, as usual? Are you only seeing
the Intel graphics offered under "Display Driver"?

Exactly, but the 3D runs well though (I presume it shouldn't if the Integrated Intel were at work instead of the Nvidia) ...just that i cannot get any shining on the fuselage...and I 've lost the track ir ability , impossible to tick the TIR box in the options menu...go figure...maybe something is corrupted and I am about to desinstall and install again ...thanks for answering , PV1 !

Yes, unless you have the umm, I think it's called Intel HD4000
(and why would you if they've given you an nVidia chip?) then
the Intel graphics typically won't even succeed in starting
the 3D.


not sure, that may be a feature of the current renderer settings,
ie. in the code. Not exactly my field; but you can fool about with
aircraft surface appearance by meddling with the .fx files. I wrote
a bit about it here: http://www.a2asimulations.com/forum/viewtopic.php?f=10&t=30369&p=230261



Well, you can always edit the TIR settings directly in the
bdg.txt file - see the manual, page 161, but also note the
TIR guide in ch. 2, in particular p33, which notes that TIR
must be enabled manually before starting BoB2.

thank you PV...now I have the "english text" crash...

OK, things that these days can cause a BoB2 crash:

#1: windows 8, and 8.1
Something in win8s does not like how BoB2 uses d3dx9.dll, and
gives a crash, after about 2 to 5 minutes of flight. There may
be a cure by moving up to W10 (I still don't know where Win9
went), but that currently rests on one report, and it's not
fully satisfactory - 3D exit is crippled, and thus campaign data
may not get written.

#2: Any machine with less than 2.5GB RAM will run into trouble
with patch level v2.11 and above when set on full eye candy;
32 bit OS machines need to also have a tweak to enable RAM
above 2GB to be used.

Those are the outstanding known issues. For other crashes,
we dig and try to deduce the problem.
All BoB2 crashes say "english text". This will generally also
write a crashlog.txt file i the BoB2 root folder. The file
gets appended on the bottom with each crash, until you delete it.
The main diagnostic information occurs in the lines starting with

------------ Begin of section written with bob.exe, Build/Rebuild all date:

and continuing through the stack dump past the system summary to the first
few lines of "Module list: names, addresses..." . On the way, there is a
line in the section following the stack dump which starts
"Error occurred at .." and provides the date of the crash. Usually the
most recent entry, at the bottom of the file, is the one of interest.

Were there a coder available, much detail could be extracted from
this log. However, these days, there's only me, and I know a little
bit from reading the assessments from previous coding members of the
BDG, to provide some limited idea of what the log indicates, at least
to the point of whether it is a real problem inside the bob2 code
(very rare) or, more typically, an instance of BoB2 and the particular
windows environment not getting along well. If you want to post that
data, I can look at it, and see what I can deduce.

Very nice from you! I 'll try first to do a 2nd install somewhere else on another HD and tell you what's going on .

cheers !