[Colonol Dekker]

Good old Invisible beam bug... You gotta love it.

I'm running 3.6.10, and the MV_3_6_10.vps  and the here are my command lines.

-spec -glow -env -mipmap -nomotiondebris -normal -dualscanlines -orbradar -rearm_timer -ship_choice_3d -3dwarp -warp_flash -snd_preload -fps  -mod mediavp

Everythings fine and i've no stripes anymore

[colecampbell666]

Corrupt VP?

[Colonol Dekker]

Not as far as i can tell.........Those command lines were ripped straight from the launcher6.ini.

I'm running my latest hardware drivers too... as noted in the GEForce driver sticky at the top of this board.

Heres my layout..

[img=http://img88.imageshack.us/img88/3729/grab1qi4.th.jpg]

[img=http://img230.imageshack.us/img230/148/grab2td9.th.jpg]

Hope it helps i'd run debug for you guys,  but i wouldn't know where to start.

[colecampbell666]

Select the build in the launcher, at the top (preferably a 3.6.10 debug build) and run the game. Play a mission or something which uses the files, and quit. Upload the fs2_open.log that you find in \FreeSpace2\data.

[Colonol Dekker]

WHOAaaaaaaaaaaaaaa.....

I didn't even get to pilot select with that debug...

here's the txt log.
Enjoy

[attachment deleted by admin]

[colecampbell666]

Code: [Select]

Found root pack 'C:\games\freespace2\fs2demo.vp' with a checksum of 0x141e5995Give it its own folder.

Code: [Select]

WARNING: "Too many beam sections for weapon BFRed - max is 5" at weapons.cpp:2984Therein lies your problem. Try moving the file above.

[Colonol Dekker]

Moved the .vp

Getting errors still.

Text attached.

C'mon Colecambell666 use that brain and make it work

[attachment deleted by admin]

[colecampbell666]

Looks like either a corrupt VP, or a rogue table. Check all the "data/tables" folders (in mediavp and in the root folder) And "mediavp" should be "mediavps".

I'll have to find the checksums for the .VPs, kara will have them.

Did it crash this time? (doesn't look like it) Where were you when it did?

[Colonol Dekker]

I just kept clicking no to stay in game and left normally. I thought the debug.txt would get populated with more info if i stayed in game. But i'm afraid it'll have to wait til later as i've just been round the block believe it or not and i'm going to sleep. Appreciate all the help so far Cole. (debug=death on my phone text )

[Wanderer]

Do not touch the root_fs2.vp!

Problem is caused by the beta state 3.6.10 mediavps.

[Colonol Dekker]

I'd never touch root.fs2. I'm not illiterate just non-code compliant. So what about these media.vps? Is this a common problem and are there patches or is there anything i can do to provide more information?

[Wobble73]

You are running Vista aren't you? Could be related to that, also, flush your cache folder in the data folder, That may help? 

[Colonol Dekker]

I've flushed the media.vp cache already. I'll try the standard data/cache too. BRB. . . . .

[Colonol Dekker]

Right, .  .  .  .  .that fixed it. (175 items)
Worth noting for other people
Wobble you're a frickin genius. Cheers all.

[Wanderer]

The beam problems aint gonna go away though in the beta mediavps with that.... The problem is the tables DaBrain got from Bobboau (AFAIK) that are actually build to use the code change Bob has made to his local copy. So for example support for more than five beam textures or type 2 tiling method does not exists. There is nothing you can do about it unless you either wait for the real release or extract the problematic tbm files from the beta mediavps, place them to data\tables of your mod directory and edit them locally.

[Colonol Dekker]

But my games working fine now. Why would i bother with all that. If it aint broke don't fix it i always say

[Wobble73]

I always flush the folder everytime I make changes to my FSO setup, (New media vps etc.) A few people have had problems that have been fixed by clearing the cache. It may be worth pointing this out to a few people. So when they release a new VP set they put a read-me in telling people to do this!