[quote name='Cheezeman' post='1094946' date='Jul 29 2010, 03:15 AM']Definitely fixes the problem, thanks OP! Seems like my framerates have REALLY taken a beating since replacing the file though... does it take significantly more processing to render the xhair in 3d as opposed to 2d??[/quote]
Actually now that you mention it, yes, I have felt like my fps dropped a bit too /confused.gif' class='bbc_emoticon' alt=':confused:' />
[quote name='Cheezeman' post='1094946' date='Jul 29 2010, 03:15 AM']Definitely fixes the problem, thanks OP! Seems like my framerates have REALLY taken a beating since replacing the file though... does it take significantly more processing to render the xhair in 3d as opposed to 2d??
Actually now that you mention it, yes, I have felt like my fps dropped a bit too /confused.gif' class='bbc_emoticon' alt=':confused:' />
[quote name='Cheezeman' post='1097755' date='Aug 2 2010, 05:20 PM']I tried comparing the files but they are HUGE and there are HUNDREDS of lines difference between them with no discernable pattern. Further, all the options are pretty crypticly named with no well-defined structure, so I don't think there's an easy way to go about it. /confused.gif' class='bbc_emoticon' alt=':confused:' />
Maybe someone a little better with code could take a look....?[/quote]
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
[quote name='Cheezeman' post='1097755' date='Aug 2 2010, 05:20 PM']I tried comparing the files but they are HUGE and there are HUNDREDS of lines difference between them with no discernable pattern. Further, all the options are pretty crypticly named with no well-defined structure, so I don't think there's an easy way to go about it. /confused.gif' class='bbc_emoticon' alt=':confused:' />
Maybe someone a little better with code could take a look....?
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
[quote name='Cheezeman' post='1097755' date='Aug 2 2010, 05:20 PM']I tried comparing the files but they are HUGE and there are HUNDREDS of lines difference between them with no discernable pattern. Further, all the options are pretty crypticly named with no well-defined structure, so I don't think there's an easy way to go about it. /confused.gif' class='bbc_emoticon' alt=':confused:' />
Maybe someone a little better with code could take a look....?[/quote]
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
[quote name='Cheezeman' post='1097755' date='Aug 2 2010, 05:20 PM']I tried comparing the files but they are HUGE and there are HUNDREDS of lines difference between them with no discernable pattern. Further, all the options are pretty crypticly named with no well-defined structure, so I don't think there's an easy way to go about it. /confused.gif' class='bbc_emoticon' alt=':confused:' />
Maybe someone a little better with code could take a look....?
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
[quote name='gespo89' post='1103458' date='Aug 13 2010, 01:20 AM']Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.[/quote]
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
[quote name='gespo89' post='1103458' date='Aug 13 2010, 01:20 AM']Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
[quote name='gespo89' post='1103458' date='Aug 13 2010, 01:20 AM']Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.[/quote]
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
[quote name='gespo89' post='1103458' date='Aug 13 2010, 01:20 AM']Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
[quote name='kitch9' post='1106466' date='Aug 20 2010, 07:59 AM']I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?[/quote]
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
[quote name='kitch9' post='1106466' date='Aug 20 2010, 07:59 AM']I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
[quote name='kitch9' post='1106466' date='Aug 20 2010, 07:59 AM']I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?[/quote]
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
[quote name='kitch9' post='1106466' date='Aug 20 2010, 07:59 AM']I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
Edited the current package.mft using the info posted by gespo89
Tested working, fixes all Multiplayer maps (Map Pack 6), no crashes
Punkbuster/PBBANS Safe (At time of posting)
Single player is also fixed, but untested.
Been using this for some 2 weeks now.
Noticed a new disclaimer on the Nvidia 3D games list.
[url="http://www.nvidia.com/object/3d-vision-3d-games.html"]http://www.nvidia.com/object/3d-vision-3d-games.html[/url]
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
Edited the current package.mft using the info posted by gespo89
Tested working, fixes all Multiplayer maps (Map Pack 6), no crashes
Punkbuster/PBBANS Safe (At time of posting)
Single player is also fixed, but untested.
Been using this for some 2 weeks now.
Noticed a new disclaimer on the Nvidia 3D games list.
[url="http://www.nvidia.com/object/3d-vision-3d-games.html"]http://www.nvidia.com/object/3d-vision-3d-games.html[/url]
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
Looking for a response from Nvidia. C'mon guys, this is one of my favorite 3D games. Give us an update pleez!!!! /confused.gif' class='bbc_emoticon' alt=':confused:' />
Looking for a response from Nvidia. C'mon guys, this is one of my favorite 3D games. Give us an update pleez!!!! /confused.gif' class='bbc_emoticon' alt=':confused:' />
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
Actually now that you mention it, yes, I have felt like my fps dropped a bit too
Actually now that you mention it, yes, I have felt like my fps dropped a bit too
Maybe someone a little better with code could take a look....?[/quote]
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
[b]BundleTarget package:levels/sp_02/ingame-00.fbrb[/b]
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
Maybe someone a little better with code could take a look....?
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
Maybe someone a little better with code could take a look....?[/quote]
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
[b]BundleTarget package:levels/sp_02/ingame-00.fbrb[/b]
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
Maybe someone a little better with code could take a look....?
Well, I haven't tried using it as a fix though, but I went poking through and comparing the old file and the new ones, and I found out what part specifically breaks the 3D. For every map in the new file, there is a line equivalent to this:
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
BundleSource game:levels/sp_02/ingame-00.fbrb
[b]BundleTarget package:levels/sp_02/ingame-00.fbrb[/b]
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.[/quote]
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
BundleSource game:levels/sp_02/ingame-00.fbrb
[b]BundleTarget package:levels/sp_02/ingame-00.fbrb[/b]
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/[b]sp_common[/b]/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.[/quote]
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
BundleSource game:levels/sp_02/ingame-00.fbrb
BundleTarget package:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_02/ingame-00.fbrb
BundleTarget game:levels/sp_common/ingame-00.fbrb
That for example is for single player map 2 (sp_02), and the bold line is what breaks the crosshair for that map. In the old file, it was BundleTarget package:levels/sp_common/ingame-00.fbrb instead. Changing the line back to common or simply deleting it all together fixed this but I haven't attempted to make this change for all of the maps as, while it seemed to work fine during my brief test on one map, I don't want to risk getting nailed by PunkBuster trying it in multiplayer and I don't know what other functions it handles besides the crosshair. I figured I'd post this though so if any of you want to tinker with it on your own, you know where to start.
I've been using a modded Package.mft for a week now to get the 3d crosshair........ If play rush mostly and if I avoid the White Pass map all seems to be ok. Punkbuster does not scan games files whilst playing so after 20 or so hours I have never been kicked.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?[/quote]
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?[/quote]
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
Anybody fancy seeing if they can enable the 3d crosshair for the rest of the maps by editing the Package.mft?
Well, I changed the lines as I mentioned in my last post and the crosshair was working on all of the conquest maps at least. I would imagine the problem you had was with because White Pass was new to rush in the last patch? I don't play rush so I wouldn't know. If so, the proper file references for it would be absent in the old package.mft, causing a crash. Anyway, when I changed the lines to sp_common for each map as I mentioned in my last post, it didn't crash on any map but the new map (port valdez conquest) had a white box instead of the little display that shows who controls what points. You could still check it by pulling up the map though. In addition, the performance seemed to be pretty poor but I just got 3D vision so I don't have anything to compare it to before the attempted fix. It could just be my rig is a bit underpowered for this.
Tested working, fixes all Multiplayer maps (Map Pack 6), no crashes
Punkbuster/PBBANS Safe (At time of posting)
Single player is also fixed, but untested.
Been using this for some 2 weeks now.
Noticed a new disclaimer on the Nvidia 3D games list.
[url="http://www.nvidia.com/object/3d-vision-3d-games.html"]http://www.nvidia.com/object/3d-vision-3d-games.html[/url]
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
See Attachment
Tested working, fixes all Multiplayer maps (Map Pack 6), no crashes
Punkbuster/PBBANS Safe (At time of posting)
Single player is also fixed, but untested.
Been using this for some 2 weeks now.
Noticed a new disclaimer on the Nvidia 3D games list.
http://www.nvidia.com/object/3d-vision-3d-games.html
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
See Attachment
Tested working, fixes all Multiplayer maps (Map Pack 6), no crashes
Punkbuster/PBBANS Safe (At time of posting)
Single player is also fixed, but untested.
Been using this for some 2 weeks now.
Noticed a new disclaimer on the Nvidia 3D games list.
[url="http://www.nvidia.com/object/3d-vision-3d-games.html"]http://www.nvidia.com/object/3d-vision-3d-games.html[/url]
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
See Attachment
Tested working, fixes all Multiplayer maps (Map Pack 6), no crashes
Punkbuster/PBBANS Safe (At time of posting)
Single player is also fixed, but untested.
Been using this for some 2 weeks now.
Noticed a new disclaimer on the Nvidia 3D games list.
http://www.nvidia.com/object/3d-vision-3d-games.html
**The patch 553292 for Battlefield Bad Company 2 is causing the crosshairs in the game to no longer render in 3D. We are working with the developer to fix this issue in a patch that will restore the experience to 3D Vision-Ready for that game.
See Attachment
The backup of the original I made seems to be no longer existent :\
The backup of the original I made seems to be no longer existent :\
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
<b>Memory:</b> 6GB DDR3 RAM (Kingston) <b>Graphics:</b> GTX 260 (216 cores, physX); EVGA GTX 480 SC
<b>OS:</b> Win7 Home Premium 64-bit / Vista Home Premium 64-bit
<b>Hard Disks:</b> 750GB + 500GB <b>Tower:</b> Antec 'Twelve Hundred' Gaming Tower
<b>Monitors:</b> 24" ACER GD245HQbd 120Hz 1920*1080 + 22" widescreen LCD 1680x1050
http://bit.ly/Bluesteel
The backup of the original I made seems to be no longer existent :\
The backup of the original I made seems to be no longer existent :\
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
<b>Memory:</b> 6GB DDR3 RAM (Kingston) <b>Graphics:</b> GTX 260 (216 cores, physX); EVGA GTX 480 SC
<b>OS:</b> Win7 Home Premium 64-bit / Vista Home Premium 64-bit
<b>Hard Disks:</b> 750GB + 500GB <b>Tower:</b> Antec 'Twelve Hundred' Gaming Tower
<b>Monitors:</b> 24" ACER GD245HQbd 120Hz 1920*1080 + 22" widescreen LCD 1680x1050
http://bit.ly/Bluesteel
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!
As Bad Company 2 is a "3D Vision ready" (!!!) game there shouldnt be ANY issues! You are losing credibility by putting awarding the game as state of the art although it just does not work!