Supreme Cmdr

LOL!!

Yeah. And it is described in the VCF as well as in the MISCON briefing.

Tonite I'm going to create a scenario consisting of only Nightstars to see what the furor is about, cuz it works just fine here.

quote: Originally posted by Captain Awesome: But freelancer and X2 require the brain power of a half asleep, retarded gopher to play.

cool. Maybe it was just a browser glitch before.

quote: Originally posted by Fuller: The assumption that the Bridge Viewer and TacOps can only be powered by the nuclear reactor just does not have a solid base. Energy is enery regardless of origin (light or Radine). shyeah, right. But hold that thought.

quote: Originally posted by Sard: Still no serial number acceptance... What does that mean?

It doesn't have an index. Whats the use/point in crying over spilled milk? Why don't you just thank the Gods above that you actually have a manual to complain about?

That makes sense because Eclipses method uses the +connect parameter which sends you directly to the server. Since you have friends connected and XFire is passing the +connect and other params (thereby bypassing the in-game browser), this will work and thats why it does. If you don't have friends connected and you try using +connect, then it won't work because there is no IP to pass to ucmp.exe. In which case, it will be ignored and then try to start the game. Of course, it won't start without the /c parameter which launches the in-game browswer.

Check your graphics/sound card settings Make sure you patch PROPERLY Put your system specs in your sig!

quote: Originally posted by Shingen: I know... I was just playing. Yeah I know. But I still had to explain why I'm coming off as being all soft and stuff.

quote: Originally posted by Darkreaver1980: Thanks for your Reply. About the Valid Target, is a enemy Marine standing 0.1 km away from my own Marines not a valid one? The problem with escort (for marines) is that they will try to stay as close to the object they are escorting as possible. They will rarely fire from where they are, unless the target fires first. I have been thinking of merging the defend AI rule/logic into the escort rule/logic because with defend, they can fire without chasing after the target and getting killed. Once I'm done with all this multiplayer tweaking, fixes etc, I'm going to look into that some more because escort (when used with marines) can get you killed - especially if you have low AI marines. quote: edit: hey nice Idea, have to read the manual again, missed the thing that i can split up my marines + Assign Team Leaders. Can i do this in Instant Action Missions to?yeah. As long as marines are escorting you, you can give them orders. quote: tryed SAD in Instant Action Mission: same again, they only follow me?! Have i screwed up my installation? (Priority List shows them as: SAD / Following) [/QB]Your installation is fine. They have a tactical state and an orders state. The tactical state you are seeing, is SAD. The orders state (which you are not seeing) is ESCORT. If you want to completely detach them from your orders stack, do this : Activate the DIE and pick a marine (leader), object (target) or whatever Press CTRL+P to designate it Search for the marine (escort) you want to mess with, then press P to add him to your priority list Quit the DIE Activate the PLV and cycle to the [escort] marine you selected above Activate the TOM and give that [escort] marine an order EXCEPT the F1 order. e.g. if you designated a hostile target in step #1, you would give the [escort[ marine and F3 command. If you designated a friendly [leader] marine, you would give F2 command. Using the above method, you can also split your marines into teams. Just designate (CTRL+P) the first marine to be leader of team A. Then give other marines the F2 order to this marine. Then designate (CTRL+P) another marine to be leader of team B. Then give other marines the F2 order to this marine. Now, if you give leader A and B, the F1 order, they will follow you, their escorts will follow them - and hopefully when hostiles show up, all hell will break loose. In fact, by doing it this way, you don't have to worry about giving orders to ALL your marines. e.g. you could give leade A and B the F4 (SAD) order. Thats only two marines. All the others will follow them etc. So, if you have ten marines, you only have to be ordering two of them around. And if they dies, just pick one of the others in the team to be the new leader. btw, when the leader of a team is killed, the escorts assigned to him, will all go into SAD mode. So you need to pay attention to this or you will lose them.

*sigh* I'm just trying to be tolerant of newbies; hoping that they catch on real quick. I'd rather delete posts, express my displeasure etc than ban people (I haven't banned anyone in almost two months and I'm having withdrawal symptoms) It takes some time for some people to realize that when you go to someone else's house - you abide by THEIR rules. Most people have this idea that because the Net is - supposedly - free, that means every URL on the Net is a free-for-all jamboree with a fully functional democracy. I guess they never heard of Derek Smart's forums.

quote: Originally posted by Captain Awesome: Woah, relax man. What I mean is that you could have put an index in at the back. There's no index at the back. How does that equate to this? The manual is not very detailed or explanitory. It really assumes prior knowledge. quote: Because someone who wants to, for example, learn how to assign crew members to different stations wouldn't know to look for the section explaining the tactical computer.If you read the Tactical computer section, you would. You have no business USING the Tactical computer to moving people around, without FIRST reading ABOUT that Tactical computer. quote: However, I felt as though it was written for someone who is familliar with the battlecruiser series. I guess you must be different from the other peopls who are new to the game and who understand the manual. quote: PS.In the "Crew Attributes" section, it discusses artificial intelligence, fatigue factor, life factor, dogfighting skill, combat missions, combat kills, and bombing accuracy. Nowhere is hunger factor mentioned.Just like the missing parts of section 9.2 which are included in the manual addendum, that attribute (which appears in the BCM Gold manual p79) was probably incorrectly deleted when the UC manual was being done. Thats the same thing that happened to section 10.0 for example, and which I included in the addendum. HOWEVER, had you read p72, paragraph 5 of the manual, you would have seen the discussion about Nutripaks, hunger etc. quote: PPS. You got your 20 bucks for me, so no matter what I say about the manual it's you who gets the last laugh Don't be cheeky. The amount I see from your measly $20, is not enough to pay for my time, let alone aggravation.

quote: Originally posted by Captain Awesome: Alot of hate in these forums hate? you're kidding, right?

In escort mode their job is to protect you IF there is a valid target within range. If you don't want to use escort, then use sad. The reason you see them run off in sad mode is because they go searching (SAD = Search & Destroy) for targets, instead of waiting for targets to come. If you release them from escort and change them to sad, it is the same as given them a weapons free order - meaning that they engage at will, without waiting for further orders, protecting you or whatever. What you should do is split them up into teams. Give two team leaders sad orders. Then have the others escort each team leader. Or something like that.

OK, can you ladies get to the bottom of this please so that we know what works and what doesn't?

quote: Originally posted by Darkreaver1980: On Tom its writen: "Escort/Defend Me". Ok, theyre nice Bodyshields LOL!! yeah, but they will also engage any hostile that threats you. quote: Hmm, better i switch every Marine to SAD when enemy Marines are closingIf you don't keep an eye on them, they will take off and get killed if they run into overwhelming odds.

Dunno, I don't do it by country. But if I were to guess, I'd say it was the UK

quote: Originally posted by Mordax Blyrr: Any news about when you will add the XFire entry into our profile page so we can all be one happy little family, SC? LOL!!! OK, will do that now Man, you guys, you guys.

quote: Originally posted by MadFox: Hmmmm... Is there any easier way to identify the arcs? No. They are not something you can draw. They are algorithmically generated.

There are vectors in each turret which indicate where the shots come from - otherwise the engine won't know (e.g. it could very well fire from a missile launcher). The vector itself has nothing to do with the PTA system. That vector is only a seeding point and from there, the arc calculations determine the direction of fire. In your asciigram above, that turret would not fire backwards (into the ship) or at any angle which would cause it to actually hit itself. And if you grabbed a protractor and checked the degrees, you will be able to determine the coverage of that turret based on the target's orientation.

Update from Macrovision, edited and formatted for the general public. quote: What we found that this debugger’s message is NOT coming from SafeDisc itself. This debugger message shows a Red Cross mark with the message Unload the Debugger and Try again. Here may be the cause of the debugger error which you have reported: Our engineers found this on a web site for a product called Blaze Media Pro. If you search for the exact error message you will also get a few other hits e.g. CDFreaks, where people have reported the problem on their machines. According to the text below, the message is caused by DivX. One of the hits found was on a OpenGL website. It is probably the case that the DivX code thinks that WE (SafeDisc protected program) are the debugger :-) Although the text below mentions reverting to an earlier version of DivX, I think there may be a more recent version which fixes the problem. "I am attempting to convert video files, but the following message is shown: Debugger detected - please close it down and restart. Windows NT users: Please note that having the WinIce/SoftIce service installed means that you are running a debugger. I do not believe I am running a debugger. What could be the problem?" This error is caused by DivX 5.1. The issue you have mentioned is a bug in this release of the DivX codec. The codec is actually what`s showing the error, and shutting down Blaze Media Pro because it is erroneously detecting the software as a debugger. You can uninstall DivX 5.1 and revert to DivX 5.05, and you will no longer have this problem The fix appears to be to try and update (or downgrade) the DivX drivers. From the information we found , it won't just be SafeDisc products which have this problem.

Update from Macrovision, edited and formatted for the general public. quote: What we found that this debugger’s message is NOT coming from SafeDisc itself. This debugger message shows a Red Cross mark with the message Unload the Debugger and Try again. Here may be the cause of the debugger error which you have reported: Our engineers found this on a web site for a product called Blaze Media Pro. If you search for the exact error message you will also get a few other hits e.g. CDFreaks, where people have reported the problem on their machines. According to the text below, the message is caused by DivX. One of the hits found was on a OpenGL website. It is probably the case that the DivX code thinks that WE (SafeDisc protected program) are the debugger :-) Although the text below mentions reverting to an earlier version of DivX, I think there may be a more recent version which fixes the problem. "I am attempting to convert video files, but the following message is shown: Debugger detected - please close it down and restart. Windows NT users: Please note that having the WinIce/SoftIce service installed means that you are running a debugger. I do not believe I am running a debugger. What could be the problem?" This error is caused by DivX 5.1. The issue you have mentioned is a bug in this release of the DivX codec. The codec is actually what`s showing the error, and shutting down Blaze Media Pro because it is erroneously detecting the software as a debugger. You can uninstall DivX 5.1 and revert to DivX 5.05, and you will no longer have this problem The fix appears to be to try and update (or downgrade) the DivX drivers. From the information we found , it won't just be SafeDisc products which have this problem.

quote: Originally posted by spamllama: I figure what happened - I think. An enemy fighter must have looped behind the station and my PTA turrets fired. Wraith must have fired back, and my computers identified it as an enemy. Yep. That sounds exactly like what happened. The PTA turrets do not have IFF logic, so they don't care whats in the way of their target. They'll just fire. And if you fire upon a friendly target for too long, you become a threat to them and they will then open fire. You should be court-martialed