Jump to content

actrade

Members
  • Posts

    15
  • Joined

  • Last visited

    Never

Everything posted by actrade

  1. The one area that he does score some points with me Derek, is about the use of acronyms in the manual. I found myself constantly flipping back and forth in the manual trying to remember what MTAR, etc. meant. Perhaps this speak is no problem for veterans, but for newbies, I did find it more difficult than it needed to be. I did serve 6 years active duty USAF, so I know how easy it is to speak in acronyms I thought he missed the boat as far as complaining about gameplay as I find it refreshing to play a game that isn't tightly scripted, while others will claim the game "wanders." Go figure.
  2. quote:Originally posted by vogelap: After any session playing BCM, my system will successfully return to the desktop, but when I try to shut down, it LOCKS UP the machine and will respond only to a warm reboot and has to run scandisk. I run EndItAll to delete all non-essential background programs before running BCM. This instability only happens when I run BCM... Any ideas what could be causing this, or how I can fix it? I used to have WIN98SE and used End It All, and in all cases, when I logged off the computer, the computer hung. The problem is that one of the files that EIA shuts down, is needed to shut your system down normally. I can't remember which one it is, so you'll have to experiment.
  3. quote:Originally posted by Mr_Paris: Okay here goes the Report... Installed the new SB driver, then re-installed the patch , played for about a hour then a CTD when asessing certain systems as in Navcom , although if i quick save adn then use the other sytem of going to Navcam via tacops , again no major problem....... Mr_Paris Well, here's my report. No CTD since I installed the new SB drivers (fingers crossed) I played for about an hour or two tonight with no probs, so drivers definately the cure here. Regards
  4. quote:Originally posted by InversionTheory: Ok here goes... ------------------------------------ SYSTEM INFO: PII 450MHz 384MB SDRAM 9.6 GB free hard drive space 8x DVD-ROM 16x10x40x CD-RW Windows XP Pro build 2600 XP Application Compatibility Update ------------------------------------ During install, I receive the "Error 1311: Source file not found F:Data.Cab. Verify that the source files exists and that you can access it". I did that. Couldn't find any problems there. I tried various install methods, including: the InstallShield Setup file, bcmsetup.bat, and the MSI package. I also tried running each in each of the compatibility modes. I visually inspected the CD for obvious damage, and found none. I even tried accessing the Data.Cab file myself, and found that I could successfully extract files manually. Out of sheer desperation, I even put it in my CD-RW drive to see if it was a drive problem. No go. What do you think? Hardware problem? Software problem? Defective disk? I'm gonna check and see if I can get it to install on another computer before I give up and swap it for a different copy. If it is my hardware, don't worry, I won't *****...I'm about to buy a new computer anyway (nothing like giving yourself a Christmas present). Thanks for your help. Had the same problem the other night myself. It just about drove me nuts. First, I got the error message while installing the RC9 patch, then I got it while reinstalling the game. I solved it by restarting my computer and trying it again. These problems crept up as I was installing/uninstalling/reinstalling on back to back to back occasions. I ended up A. unstalling the whole mess B. shutting down my computer C. ran reg cleaner application D. reinstalled without problems. Also had something strange happend that the SC may want to be aware of, even though it may be a wild goose chase I went to download RC9 and saw that the fileplanet servers were full except for New Zealand. I downloaded RC9, installed, and kept getting the same error as InversionTheory did during the patching process. Downloaded it again from the LA server and installed with no problems. Go figure.
  5. quote:Originally posted by Mr_Paris: More Info :- If u acsess a system like Tacops and then navigate to Navtron Computer and set course then back to tacops u DO NOT get the CTD when u log off from Tacops..... MR-Paris Mr. Paris and SC, I noticed that you and I, as well as others who are experiencing CTD, have SB Live/Live Value cards. We both are also using Win XP. I ran a little experiment last night. I went through every step in the FAQ and continued to get a repeatable CTD until I lowered my sound acceleration. I got through a full save without a CTD, but about 10 minutes later, CTD. My sound also started to deteriorate with time (after lowering acceleration), sounding fuzzy and distorted, which combined with the better stability, led me to believe I was on the right track. Then I realized something. I had forgotten to reinstall the newest SB Live drivers http://www.soundblaster.com/support/winxp/...vedrvupdate.asp when I reinstalled Win XP! I noticed Mr. Paris that you are running drivers dated 11/1/01. The new ones are dated 11/29/01. Although XP does install SBL drivers, they aren't the most current. Anyhoo, I proceeded to run BCM for about an hour with no CTD, also with full sound acceleration enabled! It got late so I had to get some shuteye, but will continue to test tonight. Question for the SC. I didn't have any problem running BCM patched with the "official patch". Solid as a rock. I seem to remember, but I'll be damned if I can find where I read it, you saying that after the first official patch, the RC patches MUST use Direct X 8.1 drivers. The download page says all patches must use 8.1, but did the first patch not require it? Just musing as to why patch 1 is solid and the RC9 patch isn't? Hopefully, tonight I'll run without a CTD and prove that this is a driver issue. Mr. Paris, please download the new drivers and let me know if this helps. Regards.
  6. quote:Originally posted by Mr_Paris: Hi SC, I seem to be having a CTD problem specifcally around acessing the Navcomputer when in flight , if i try to change a destination i get a CTD, now if i acsess the Nav computer but do not selct a new destination and click log of no problem , yet when i chage destination and then click log of i get the CTD,(on a trade run from earth to Pluto) strange eh ? ive reproduced this 5 + times, i have the save game if u want it......i have all the latest drivers for my Video card and sound card ........ MR-PARIS Rats! I thought I was completely stable, but also had the exact same thing happen to me as Mr. Paris here. It also is reproduceable.
  7. quote:Originally posted by actrade: I hate to post something like this, but I'm out of answers SC. After much RTFM, I finally got into actually playing the game quite a bit I've been bopping around here in there with the different RC's, but finally got a chance to play in depth with RC9. All last night, one CTD after another, with no discernible (sp?) pattern, completely random, often without me even touching the keys and usually 10-15 minutes into the game. Tried both roam/campaign, same result. In frustration, I went back to the official patch version 1 (only after complete reinstallation as to avoid random variables) and have since played hours without any problems. Did a reinstall, installed RC9 and back to CTD, once again without touching anything or doing anything in particular. Went back, reistalled, installed patch 1, no problems. Installed RC9 over the top of patch 1 (thought I'd try it to eliminate another variable), CTD after 10-15 minutes. Here's my dilema SC. I don't know if this is unique to RC9 or was introduced in one of the other RC. The only way I see to solve this is to try other RC's and see which one (if any) introduces the CTD. I'm on a 56k modem and it will be awfully time consuming, but I'd like to try it so I can report back to you which RC is causing the problem. RC9 is the likely culprit as I've never CTD before, but as I said, RC9 is the one I've played the most with. I do feel that I played the other RC long enough to see a CTD, but didn't play for hours to verify. Sorry for the rambling post but I wanted to be as clear as possible. BTW, is there anyway to send a crashlog to you? Perhaps this would be easier? I also recently reinstalled WINXP and all my drivers, so they should be rather clean. I also reinstalled my VIA 4-1 drivers. Will attempt the RC9b patch and let you know. Regards. RC9b solved the problem. Good job, SC. Stable as a rock.
  8. I hate to post something like this, but I'm out of answers SC. After much RTFM, I finally got into actually playing the game quite a bit I've been bopping around here in there with the different RC's, but finally got a chance to play in depth with RC9. All last night, one CTD after another, with no discernible (sp?) pattern, completely random, often without me even touching the keys and usually 10-15 minutes into the game. Tried both roam/campaign, same result. In frustration, I went back to the official patch version 1 (only after complete reinstallation as to avoid random variables) and have since played hours without any problems. Did a reinstall, installed RC9 and back to CTD, once again without touching anything or doing anything in particular. Went back, reistalled, installed patch 1, no problems. Installed RC9 over the top of patch 1 (thought I'd try it to eliminate another variable), CTD after 10-15 minutes. Here's my dilema SC. I don't know if this is unique to RC9 or was introduced in one of the other RC. The only way I see to solve this is to try other RC's and see which one (if any) introduces the CTD. I'm on a 56k modem and it will be awfully time consuming, but I'd like to try it so I can report back to you which RC is causing the problem. RC9 is the likely culprit as I've never CTD before, but as I said, RC9 is the one I've played the most with. I do feel that I played the other RC long enough to see a CTD, but didn't play for hours to verify. Sorry for the rambling post but I wanted to be as clear as possible. BTW, is there anyway to send a crashlog to you? Perhaps this would be easier? I also recently reinstalled WINXP and all my drivers, so they should be rather clean. I also reinstalled my VIA 4-1 drivers. Will attempt the RC9b patch and let you know. Regards.
  9. I hate to post something like this, but I'm out of answers SC. After much RTFM, I finally got into actually playing the game quite a bit I've been bopping around here in there with the different RC's, but finally got a chance to play in depth with RC9. All last night, one CTD after another, with no discernible (sp?) pattern, completely random, often without me even touching the keys and usually 10-15 minutes into the game. Tried both roam/campaign, same result. In frustration, I went back to the official patch version 1 (only after complete reinstallation as to avoid random variables) and have since played hours without any problems. Did a reinstall, installed RC9 and back to CTD, once again without touching anything or doing anything in particular. Went back, reistalled, installed patch 1, no problems. Installed RC9 over the top of patch 1 (thought I'd try it to eliminate another variable), CTD after 10-15 minutes. Here's my dilema SC. I don't know if this is unique to RC9 or was introduced in one of the other RC. The only way I see to solve this is to try other RC's and see which one (if any) introduces the CTD. I'm on a 56k modem and it will be awfully time consuming, but I'd like to try it so I can report back to you which RC is causing the problem. RC9 is the likely culprit as I've never CTD before, but as I said, RC9 is the one I've played the most with. I do feel that I played the other RC long enough to see a CTD, but didn't play for hours to verify. Sorry for the rambling post but I wanted to be as clear as possible. BTW, is there anyway to send a crashlog to you? Perhaps this would be easier? I also recently reinstalled WINXP and all my drivers, so they should be rather clean. Regards.
  10. This isn't a showstopper and for now is my own fault, but it may become an issue when MP arrives. I haven't been able to figure out why my computer is auto-dialing my ISP (working on it), but I have been able to reproduce the following effect 100% of the time. 1. I'm in the middle of BCM, all other apps shut down via neat little program "End It All". 2. My computer begins to dial to my ISP (my problem I realize). 3. BCM minimizes to desktop as the dialing message pops on the screen. 4. Upon maximizing BCM, the icons along the right side of the bridge screen (shuttles/fighters/CC/missle) disappear and are replaced by a blue block instead of the proper icon when you move the mouse over it. The reason I could see this being a problem is if a user were to be accidentally disconnected in MP and the disconnection message were to pop up on the desktop, BCM would minimize to desktop. Is there anyway to keep BCM from minimizing if another app opens? I realized SC that this is likely a low priority now, but you asked for issues (first post so I hope my sys info attaches)
  11. Thank you, I didn't realize that the tutorial was based on the actual game. Perhaps that explains a lot. Thank you.
  12. Wow! Mum is the word here. I hope the manual is clear as I won't ask questions here again! Holy cow, I mean I'm a newbie, spent hours and I mean hours reading the control file trying to find the answer to my question. After reading many posts in this forum, I saw what happens to people who ask stupid questions, generally they are verbally abused, so I made a point not to post until I was literally pulling my hair out "trying to like the game." What do I mean by that? Well, I've never played any of the BC series and was impressed with what I read about it and decided to order the game on faith, prior to even downloading the demo, which took forever on my poor 56k connection. I guess it's my fault for taking the tutorial too literally, as the enemy cruiser shows up around 13:15 consistently instead of "around 13:05", which I took literally. As far as the responses suggesting the enemy was cloaked, I guess I thought the poster was messing with me as I wasn't aware that the scenario was dynamic and that sometimes the enemy can be cloaked and sometimes it isn't as the poster suggests. Sorry for the rhubarb guys, I'll just figure it out myself from here on. Thanks.
  13. I finally found out it comes at 13:15, not 13:05 as the tutorial suggests. Look guys, I'm new to the BC series and am a long time flight simmer. I've seen the board "grognards" abuse new players for years, only to the detriment of the whole genre. I asked a simple question only after surfing and reading for a day. Did no one know the answer, or was it just easier to post unhelpful answers? I'm trying to like this game and have already ordered it from EB and I'd really appreciate it if everyone would be constructive with their responses. I've seen SC verbally lash people asking questions that are in the tutorial/version revison, which I can't say I blame him, but when the tutorial is wrong, what's a newbie to do?
  14. No, I'm not cloaked. As far as the enemy carrier, according to the instructions, it should arrive and doesn't. I admit, I'm a newbie, but I spent all day looking through the discussions, revision history and FAQ with no luck. What am I doing wrong? I want to see that carrier attack my spacestation.
  15. I hope no one has already discussed this, but this is weird. I have installed and reinstalled the demo, installed the 4th mission, but when I run the 1st mission on demo #2, the enemy carrier that is supposed to show up around 13:05 game time never does. Any answers?
×
×
  • Create New...