Jump to content

VorpeHD

Members
  • Posts

    14
  • Joined

Reputation

10 Good
  1. Lol they break the sub track, then fix it only to then break the free track in the process. sheesh BW can't catch a break lol, 7.1 is starting to look faaaaaaaaaaar off...............
  2. VorpeHD

    Crafting

    More bugs: - crafting/crew mission window not updating like it's supposed to (when you get more mats, or switch to different crew mission, etc). This bug has been in the game since launch. - crafting/crew mission window getting deselecting when other windows are under it (e.g. inventory). Hopefully fixed with new UI. This bug is also older than every expansion yet still exists. - still cannot set default sorting for crafting window, always defaults to "difficulty" which is pretty un-intuitive and useless since you can still see crafting difficulty on every sorting option via color code. maybe fixed with 7.1???? pls Bio....,
  3. Weird, I first had the same issue and error. I put the fix files in its own folder and excluded the folder, that worked. I was also gonna cancel my sub if it's not fixed within 3 weeks, but honestly the game runs fine and I have the fixed exe on my taskbar, the problem is not even noticeable anymore. We can still even get updates, I'm keeping my sub regardless.
  4. I have tried that in the past, it doesn't work. you'll have to reinstall the game, or just put the old storage drive in your pc and use that. The launcher opening and closing with the fix is normal, idk if youre a steam user or have used the launcher in the past but you should know it does the same thing with the official launcher, on any cpu. Especially for old installs. Just keep running the fix, it will finish eventually, and the launcher will work. I've not heard of this fix not working.
  5. That is normal. Just keep running it until its finished, it does the SAME thing with the official launcher. When you first install the generally, on another cpu, the launcher closes and opens multiple times.
  6. agree but dunno if id say unsafe, the source code is available for all to see.
  7. The fix you linked is identical to the one on reddit though, assumed that was your post. Even the hashes and filenames match. Lol don't steal credit now, unless it's the redditor plagiarizing your work.
  8. I've been getting random rare crashed for years. So I would certainly say it's probably not the 12th gen cpu but rather the poorly optimized game and/or windows having a hiccup. Try checking even viewer or any crash logs when it happens to really see what can cause it. SWTOR crashes can be from a number of things, direct x virtualization issues, graphics drivers, the game itself, windows, etc. a lot of vectors for something to go wrong. You're on a laptop, if the cooling isnt sufficient or its filled with dust then even a strong thermal throttle could crash the game.
  9. I'm guessing you already had an account on there. I wanted to play FF but idk if they're still closed off from new subscribers. Game is so good they need to upgrade their servers, take a lesson or two from them BioWare.
  10. Lol wish I had been able to do that, I got alder lake on launch fearing it would become unobtanium. Took awhile for this thread to pop up. Almost sold my old 4790K system, now I'm using it as well for the time being. Game runs pretty good with that and my old 750Ti all considering. Can't wait for the fix to finally enjoy some 165hz swtor
  11. Some factors like this only affected a specific platform (Intel 12th gen), the issue being with the launcher and not the game (rare), and the rush to push out 7.0 are all why it's still not fixed. 7.0 got delayed, someone here did their job for them, and the list of 12th gen subscribers going up during the holidays as people get new PCs all gives them no excuse to have us wait beyond January for the fix. We pay their salaries after all.
  12. Devs took so long a community member found the issue, and even fixed it at that! BioWare support already made a post in this thread, they have ZERO excuse now to not come back in here. To fix this in January, preferably within a couple weeks. Literally handed to them on a platter, something like this almost never happens. Good thing the game is fine, the archaic launcher is nowhere near as difficult to debug. Don't even need a full update, just let us download a fixed launcher. Thing is nobody at BW probably has an alder lake CPU to test with, could explain why it hasn't been fixed yet. Now they don't even need one. I'm almost inclined to mass e-mail and tweet swtor support with the fix post above you quoted, using a screenshot.
×
×
  • Create New...