Jump to content

truedark

Members
  • Posts

    361
  • Joined

Posts posted by truedark

  1. I just want to point out that when you do optimizations you are not making optimizations to get the highest possible FPS possible. You are trying to get the most stable FPS. You want the game to run at a consistent FPS like say 20 FPS rather then 100 FPS that dips down into the 30s occasionally.
  2. When you've completely finished a planet, look at your map. There are areas still undiscovered. If you're Republic, those places are likely Empire questing zones and vice versa. The two questing zones rarely coincide.

     

    Tattooine is a good example of a planet where Republic and Empire have quests that overlap one another, and you should expect to see the other faction more often than other leveling planets there.

     

    Not what hes talking about. Taris and Balmorra have two versions. A level 16-20 and a 33-37 version. The low level Taris is for Republic and the low level Balmorra is for empire, when you go there as the other faction its the high level version.

     

    I think part of the reason for this is to save development time, rather than completely remake the planet they only need to wipe the mobs off and redesign it for later levels, however the planets do feel vastly different between their low level and high level counterpart imo.

  3. Well, as someone who used to work in the PC gaming industry a LONG LONG time ago (yeah, I feel old...) here's what I would do...

     

    1: Hire a new set of folks to look after the forum, hire two more Community Reps. One extra to look after the forums and one to look after the site. BioWare's lack of communication right now makes my days as one of Activisions staff look really rosey...

     

    2: Lock down the current running build. No game change code means that all current code lines of the game is locked in place, once that takes effect I would then direct all the resources of the devs to go through the code one more time after looking at selected threads (not all, cause most of the threads in this general forum are whiney assed kids). I would instruct the devs to look at these topics and then go through the code in a scrum developer mentality, releasing daily patches (yes DAILY PATCHES) to the test server for testing with a 1 week turn around.

     

    3: I would then make an announcement on the site that anyone who tests the game on the test server for more than 1 day a week, will have access to goodies in a new "Test Server Vendor" on the main servers as a thank you for testing the roll out patches.

     

    4: The lock down would run for an entire month. The basis would be to weed out the vast majority of the bugs in the current game code.

     

    5: I would then instruct the Community Manager's who pick a random selection of 100 people. 50 from the folks of the old beta test community, 50 from new sign ups after the launch of the game. These 100 people would be picked randomly from the user database. Then an email would be sent out to these 100 people asking basic questions about how they are finding the game. Reason i would pick out 50 from the beta is because they have been with this game since closed doors. Reason i would pick new sign up's is cause...well..they are new. These 100 people would change every 2 weeks so its not always the same 100 people giving feedback.

     

    In the days of me working at Interplay and Activision this is the kind of thing that sometimes went on if a game launch was coming up or had been released. Game development changed drastically just as I left the industry in 2000 to a more closed door attitude, back in the 90's...we LISTENED to the community...now that aint the case. It;s why there has been a serious degradation to the overall Day 1 release of PC games over the past 10 years.

     

    I can find an issue with daily patches. Back in the 90s games weren't millions of lines of codes long. Even having everyone look over the code might take an entire day. Finding an issue could take a week or more, its not as simple as it used to be in the 90s.

  4. The only way for software to even remotely damage hardware is if it runs in ring 0 or ring 1 where it can control fan speeds and other direct hardware changes. SWTOR does not run in either so it cannot do this. This means the only way that SWTOR could possibly damage your system if it made the GPU work as hard as it can and your system has a pre-existing heating/cooling issue.
  5. x-wing, tie fighter, x-wing vs tie fighter, rogue squadron, should I go on? Because there are a lot to choose from.

     

    Granted this game isn't about flight, but it's not about rail shooters either. Flying in games is just cool. I spent a lot of time checking out the world in CoH, DCUO, Champions Online, and WoW just flying/super jumping around. It also connects the worlds/zones with each other and makes the universe more cohesive.

     

    But hey, if you think a series of load screens is preferable, who am I to argue?

     

    Uhh you never flew somewhere just for the heck of it, you were there to do a job. Not dick around and fly around space because its fun. Unfortunately in Star Wars exploring space is boring lorewise because its already been done.

  6. I can see the validity in that point, but do you feel some thing are expected to be working at release that are not compared to other games releases?

     

    I've done software engineering. I've learned not to expect anything to work. Its not as simple as a line of code, a game this size likely has millions of lines of code with each programmer being responsible for maybe 50,000 to 200,000 lines of code.

  7. Well, if he's anything like me, he's very very upset that the final class boss for the Knight is unsoloable. Because, up to this point, any quest that is BY DESIGN meant to be done as a group has had [GROUP] somewhere in its name. And the final quest does not. So it leads you to believe you can actually do it, when in fact, it is going to kick you repeatedly in the face.

     

    Which in and of itself is bogus. I've done the entire questline up until this point solo. Should be able to finish the damn thing solo.

     

    Going to call ******** on this. All class quests are soloable if you play them right and with the right combination of companions.

  8. If my canon memory serves me...based upon New Hope-era.

     

    Emperor -> Agents of the Emperor/Direct Apprentice (Vader) = Grand Moff -> Military

     

    Now, following this structure you could assume that canon in the Old Republic era would be something like this...

     

    Emperor -> Agents of the Emperor/Direct Apprentice(s) -> Grand Moff = Council -> lesser-Darth -> Lord -> Apprentice -> Acolyte -> rank and file Military.

     

    Of course, this is all conjecture simply because the fluid nature of Sith hierarchy.

     

    It goes Emperor -> Dark Council -> Darth -> Lord -> Non Force Users

     

    I did not include Imperial Guard, Emperor's Wrath, or Apprentices for the reason that they are either answerable to only the emperor or their own master.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.