TA5 Bugs or Issues (Someone had to start it)

[Red Devil]

Pilot thing: I get that when copying old pilot0.dat over new one. Tried selecting first blank slot and clicking Retire Pilot?

[AHadley]

There are some rather odd texture flickers. I think something's going wrong with map layers and it shows one at a time rather than all at once, with transparency.

For some reason, I can't see any games in the MP list, and nobody can see mine. It says I'll need to configure my ports, but I've already done that.

[Commando]

IBM reported that the graphics look bad on an Nvidia MX200 in TA5.

[xSSx Grizzly]

If using Vista, run as administrator.

[TheJamsh]

It only seems to be on those damage effects. i wonder if they have any emitInherit values?

[GreenHeart]

IBM reported that the graphics look bad on an Nvidia MX200 in TA5.

someone suggest to him to update the video driver which i think seemed to work.

[Warfreak]

BTW, for those wondering, EMBM(?) Bumpmapping and full shadows no longer exist, they never worked right in the first place.

[VSMIT]

That's probably why they aren't included in the graphics options.

VSMIT.

[GSH]

If you have a GeForce MX 100/200 card, do NOT use the drivers for it that Microsoft suggests. Instead, use them from http://www.nvidia.com/object/winxp_2k_93.71_2.html here.

That link was found by this pathway: http://nvidia.com -> Download Drivers -> Download Drivers. That gets a 'Get drivers by product' page. Select product type 'Legacy', Product Series 'GeForce 2MX Series', Product 'GeForce MX 100/200', and WinXP/English, it gives the link in the first paragraph above.

As 1.3techalpha5 uses the latest DirectX SDK (Mar 2009), you should investigate newer drivers if things look odd ingame.

-- GSH

[General BlackDragon]

i have nvidea geforce 7600, so i would select geforce 7 series right?

[xSSx Grizzly]

i have nvidea geforce 7600, so i would select geforce 7 series right?

Yes 

[Steeveeo]

AV when testing out how well SRV works in TA5.

I was playing on a modified BigAssMoonMap with the IA paths and DLL added, but was made in 1.3pb3, so an outdated map format/dll may have been the issue, but not sure.

I had a C++ Runtime error pop up, then this AV.

Code Select Expand


---- Battlezone II Log File ----
//=====================================================
App version: Patch 1.3TechAlpha5 EDITOR Apr 23 2009 13:39:30
Windows version: Windows Version: 5.1.2600 'Service Pack 3' PlatformID=2

Last few battlezone.log lines (may or may not be relevant):
DIAG|            runcodes:154  |16:54:24|1077950|[View] Entering run code [SATELLITE]
ERR |        VertexBuffer:513  |16:56:17|1191393|VertexBuffer overrun (0xDEA9BEEF, 0xC0DEF00D) detected in Unlock.
ERR |                 log:1784 |16:56:17|1191406|abort() requested from '.\VertexBuffer.cpp':514
DIAG|                 log:1785 |16:56:17|1191415|End of line...
(done)

Exception code: 40000015 {Fatal Application Exit}
%hs

Message :  Unhandled Exception
Error occurred at 4/25/2009 16:56:26.
E:\Program Files\Battlezone II 1.3ta5\BZ2Edit.exe, run by Family Comp.
E:\Program Files\Battlezone II 1.3ta5\BZ2Edit.exe, run by Family Comp.
CPU: 2 processor(s), Intel(R) Core(TM)2 Duo CPU     E6750  @ 2.66GHz
     x86 Family 6 Model 15 Stepping 11
Process Memory :   1506 MB free out of   2048 MB total
Physical memory:    822 MB free out of   2047 MB total
Page(swap) file:   2713 MB free out of   3940 MB total
This exe is using 341 MB, peak use 341 MB

Fault address:  0056B685 01:0016A685 E:\Program Files\Battlezone II 1.3ta5\BZ2Edit.exe

Registers:
EAX:00000000
EBX:00625038
ECX:00000000
EDX:7C90E514
ESI:010A4338
EDI:00624FEC
CS:EIP:2E65001B:0056B685
SS:ESP:65740023:0206F7F8  EBP:0206F808
DS:10A0023  ES:620023  FS:003B  GS:560000
Flags:00000202

Call stack:
Address   Return    Function            SourceFile
0056B685  00000000  00585C32  BZ2Abort+0x0000008D
00585C32  00000000  00519DA6  VertexBuffer::Unlock+0x00000078
00519DA6  00000000  00511D81  TwirlRenderClass::Render+0x00000421
00511D81  00000000  0048A8BC  ParticleSystem::Submit+0x000000CE
0048A8BC  00000000  0048A6B0  GameFeature::FeatureVoid::Update+0x0000000D
0048A6B0  00000000  004493B6  GameFeature::SubmitAll+0x00000015
004493B6  00000000  00460CE4  Render_Satellite_View+0x00000126
00460CE4  00000000  00576510  ViewSatellite::Process+0x00000670
00576510  00000000  0045FF28  RunCodes::Process+0x0000019E
0045FF28  00000000  0046392C  ViewManager::Process+0x000000A6
0046392C  00000000  00463E59  MissionHandler::RenderOneFrame+0x0000006E
00463E59  00000000  00576510  MissionHandler::State::RunState::Process+0x00000437
00576510  00000000  004619BE  RunCodes::Process+0x0000019E
004619BE  00000000  00576510  MissionHandler::Process+0x00000011
00576510  00000000  00575F68  RunCodes::Process+0x0000019E
00575F68  00000000  00449D60  Main::MessagePump+0x00000051
00449D60  00000000  00449A4F  HandledMain+0x0000043B
00449A4F  00000000  004470E2  HandledMain+0x0000012A
004470E2  00000000  005BAED7  WinMain+0x00000059
005BAED7  00000000  7C817077  memcmp+0x00000191
7C817077  00000000  00000000  RegisterWaitForInputIdle+0x00000049


[Warfreak]

Nope, its particle related... IOW: Reamp your stuff. 

(either you have a now invalid particle or you overkilled it.)

[GSH]

ERR |        VertexBuffer:513  |16:56:17|1191393|VertexBuffer overrun (0xDEA9BEEF, 0xC0DEF00D) detected in Unlock.

Tried checking your memory for errors? That looks like a bit got flipped, not a normal overrun. 0xDEADBEEF -> 0xDEA9BEEF. Hex 'D' is bits 1101, while 9 is '1001'. TwirlRenderClass looks safe enough that it shouldn't ever have an overrun. I recommend going to http://www.memtest.org/ , downloading the .iso, burning that to a CD (as an .iso, not a file on a CD), and booting from it. Let it run overnight, and see if it comes up with anything.

Ubuntu and Win7 beta have memory tester apps (ubuntu's is based on memtest86) as well.

-- GSH

[Steeveeo]

One problem with that, no spare CDs. :/

Oh, btw, if it helps any in figuring out just what caused this, I did the following during the game:

In chronological Order:

1. I set sky.visibilityrange to 1500, fogrange to 500 1500 (I like to see very far, and I found in Pb4a that 1500 was the highest I could go before losing frames or the gorund starting to flicker).
2. I messed with the stars, using console commands such as star.size 100, star.speed 100 100, star.count 128, to make a nice, flickery starscape.
3. I caught the front pool, and then used the shift f10 topdown view to command.
4. Alttabbed a few times because people were messaging me.
5. Upon alttabbing back each time, the screen would be black except for the HUD until I moved the satview.
6. Exited satview to fight off a couple enemy scouts, went back to sat view.
7. Ordered about 5 hoverscavs to scavenge, they moved about 50-150 meters, and then the error occured.