Supreme Cmdr

quote: Originally posted by Race Bannon IV: SC I sense a new mean streak in you and it isnt pretty. You are officially on the "LUMP OF COAL" list. I have come to count on your sage wisdom, not your sharp tongue...Whats that google thing again? Good luck with your project. er, wha? quote: Originally posted by Eclipse: I think it's just an extension of the "use the search function before posting duplicate topics" comment Just ignore him. He's just being a git. Either that, or its that time of the month. quote: On topic: SC I'm interested on how your Myth TV box works out. I've been looking into setting up something like that for some time now but I haven't taken the plunge Got some of the parts and still waiting on others. I'm beginning to think that I should've just gone with BeyondTV. But its not too late to do the switch yet. I'll decide once all the HW shows up.

Weather CAN be manipulated and Scott Stevens not only has a point, there are COUNTLESS studies which back up his claims. Grayfox, only mere mortals without a fully functioning brain (they're usually called idiots) would dare refute that which they don't understand nor fathom within the scope of their intellect. *thread moved*

The craziest bundle EVAR!!

Not in this thread.

quote: Originally posted by Grizzle: Perhaps I can create a GBS script to help with testing it out. You'll do no such thing. Assuming, of course, that you know what you're doing.

..I dunno about you folks, but I quite enjoyed my bell bottoms, platform shoes (the ones where you fell three ft if you stubbed your toe) and fro.

quote: Originally posted by TSCavalier: quote:Originally posted by Cc: quote:I've noticed that sometimes when switching to Perscan when there are intruders or prisoners on board that I get a CTD with an unhandled exception error.I have experienced the same problem.But it is very intermittent. I've played for a few hours the last couple of days. It does seem to be somewhat related to viewing Perscan as intruders become prisoners and either you have resized/stretched the intruder/prisoner list, or are in the middle of doing so, or have the mouse on or around the area or something. I made a save game just as intruders came on board, then hung around on Perscan while the intruders were killed/captured. And reloaded and retried a few times. Because you never know if intruders will be killed or taken prisoner, and exactly what UI manipulations cause the crash, it's hard to reproduce, but it did crash on occasion. So, I've given up on figuring it out. Now I simply save the game right when intruders come on board, and if it crashes I haven't lost much. Also, I avoid manipulating the lists in Perscan (by dragging the lists larger/smaller). Hopefully this advice will help anyone that experiences this on their own machines (or help them avoid the problem). Since I have taken this more careful approach, the game hasn't crashed once... If it can't be reproduced, there's no point harping about it because it can't be fixed. Your posts which reek of I can't remember this etc and which are related to UC and the UCAWA demo and which bear NO relevance to this thread, have been deleted. Your last post will also be deleted. Second of all, this thread is completely unrelated to what you are talking about. The specifics as to what was causing the UCAWA crash with a certain number of intruders, is clearly documented in the VCF and has been fixed. If Grizzle (or anyone else) has clear reproducible evidence that manipulating the Perscan display at certain resolutions causes a CTD, then a new thread needs to be created so that it can be investigated.

uhm, you ever heard of Google?

nah!! Probably only the appropriations committee didn't already know this.

Brian has a write-up about the service

quote: Originally posted by DennyMala: Here I come again..... I downloaded the patch from 3d gamers and installed it without problems. Then I tried the updater (the second version) to see if everything was fine and no updates were available but it keeps telloing me that there is a new patch available: the 1.00.06. I fear I'm missing something but I can't figure it out or it can be a problem in the updating system. Can someone point me what I have to check to see if it's something on my end or not? If you download a patch and don't use the Updater, how EXACTLY do you expect the Updater to know that you have updated it? The Updater keeps the current version number in the SETTINGS.INI file. If you manually patch the game, obviously that file will be showing a different number. And obviously Updater will attempt to download the patch, not knowing that you have patched manually. If you apply a patch manually, you have NO BUSINESS using the Updater because the patch has nothing to do with Updater files and does not modify the SETTINGS.INI file. The patch only updates files it has control over, such as the UCSETUP.INI (and the registry) which will show the current patch level. And no, there is NOTHING wrong with the Updater.

Shamelessly ganked from Gamecloud: This Wall Street Journal Online story (paid registration required) reports that id Software co-founder Adrian Carmack was fired earlier this year by the rest of the co-owners of the company and is now suing his ex-teammates to have his employment contract be called invalid. According to the story, long time id publisher Activision wanted to buy the Doom, Quake and Wolfenstein franchises for $90 million last year and even thought about buying id itself for $105 million. While id CEO Todd Hollenshead has stated in the past that id doesn't feel the need to sell its company and prefers to stay private, the Wall Street Journal story claims Adrian Carmack (no relation to id master programmer John Carmack) said the real reason id didn't sell was that the other owners (Hollenshead, John Carmack, Kevin Cloud and Tim Willits) wanted him to sell his 41 percent stake in the company to them for an amount that would have been just $20 million but would have doubled to $40 million if the Activision deal went through.

We are looking into a problem with the remote servers whereby clients (players or NPCs) in hyperspace will sometimes get stuck there due to conflict between the client and the server both updating the hyperjump timer (as viewed in VDD/VID). This can cause clients to get stuck in hyperspace or show incorrect timer countdown values. This problem does NOT affect local LAN servers; only remote servers (which are subject to infrequent packet updates). We have found the problem and are currently investigating a fix.

I'm looking forward to it. Hopefully they've addressed the issues (combat and AI) in X2. If not, I guess I'll be shelving this one too.

Lots of X3 news coming out. IGN preview GameSpy Q&A GameSpot Dev Diary

Never heard of it. In fact, I can't even find it at any theatres.

quote: Originally posted by jamotto: I don't have a major problem with game publishersdevelopers including copy protection in their software, however I do expect when I run the uninstall program that it does exactly that, uninstall everything that it installed including the copy protection. In my own opionion I should not have to search the internet for a program to remove the program that should have already been removed. The problem is that even though Starforce advises the devs to include the driver removal in their game uninstall program, most NEVER do it. For whatever reason. The result is that when you uninstall the game, the SF drivers remain on the system and can only be removed using the SAME tool (linked to above) that SF provides to the devs. I don't include the SF driver uninstall in the UCAWA uninstall program either. Why? Because I have no way of knowing if another game requires them or not. So, I leave it up to the user to remove it themselves.

...and MS joins the fray. Well, it was only a matter of time anyway.

It is complete nonsense. StarForce - all versions - have drivers. Just like any other program that you can install and which has drivers. So, no notification is required. Apart from that, there are Starforce removal tools on their website as well as ALL OVER the Net. These are just alarmists (probably pirates) who are just pissed that SF actually works. In fact, has ANYONE here had ANY problem on their system related to to UCAWA using SF ProActive (which also uses drivers?). Nope.

Glad you got it resolved. BMT are pretty good about stuff like that.

Remo, send this via the internal chat list please and give me a list of FLs who are just not up to the task. They will be relieved of duty effective immediately and removed from the fleet in EVERY capacity. I don't pay for these resources so that people can screw around with my time, effort, money and resources. The next step - if this keeps up - is to disband the official fleets, kill the dB and tell everyone to piss off and setup their own servers and whatnot. Either that, or fold all fleets into Prime.

I LOVED it!! It is what I thought Red Eye was going to be. The suspense, the thrill, the mind-screwing that goes on, will most likely throw everyone off the main plot. 10/10

FLs with admin access to the dB should be checking all fleets (there is a single option right there on the main page for that) and notify FLs without admin access that there are waiting recruits.

uhm, GALCOM is one word. I guess in your leave of absence you've forgotten everything? Do you remember where the eject button is Spiro?! Welcome back!!!

quote: Originally posted by twobombs: I think that it has got to do with the depth at which the shuttle-targeter thinks that is the ground level. I often find negative numbers next to the ' target ' area. Maybe the SC can shed some light on this matter; as he coded the routines. Wrong. The crafts ALWAYS know where the ground level is. Bad pilots - even the onboard AP - are prone to errors. If I made it perfect, then whats the fun in that? If you want to see how the A/P performs, as opposed to AI pilots, set waypoints as normal, then send your AE to the craft, enable "Resume Waypoints" order and turn on the AP. You can also try it using the CALS system to see how it behaves when selecting a landing position. Various crafts have various characteristics, as do various crew members based on their AI. Also, if you do not leave a long enough distance between waypoints, the pilot will not be able to setup a near perfect landing profile. This will result in boneheaded moves like what Grizzle described above. Any time you see your craft go vertical, then dive for a waypoint, that means the landing profile has been screwed up because of the previous waypoint. The lower the AI of the pilot, the more likely he is to make things worse. I have NO idea why I'm even typing this up, given that not only is it in the manual (and tutorial), but has been discussed MANY times on this board.