I admit, I'd pay for hair DLC...
I feel so ashamed.
Do not feel shamed. I'd pay to have more armour and weapon schematics in the game. Especially single handed swords and heavy armour which doesn't look just plain odd on a female Qunari. 
Aesthetics are not a bad thing to pay more for if they're something that you want.
Yours is a noble quest op but good luck in finding supporters here. The masses are too forgiving and apathetic. And everyone has forgotten that the man who watches something wrong with apathy is nearly as much to blame as the one who does the wrongdoing. If the publishers have stopped giving s **** we ourselves are responsible for that. But then that is the state of the entire gaming community sadly.
Good luck OP, PC controls are fine, need more ability slots and the hold command needs to work better but, not game breaking. Blak hair isn't black and, I'd like more hairstyles but, again nothing game breaking.
Yours is a noble quest op but good luck in finding supporters here. The masses are too forgiving and apathetic. And everyone has forgotten that the man who watches something wrong with apathy is nearly as much to blame as the one who does the wrongdoing. If the publishers have stopped giving s **** we ourselves are responsible for that. But then that is the state of the entire gaming community sadly.
lmao BSN is 'too forgiving and apathetic'? You weren't here on launch day now were you?
Honestly he won't find supporters anywhere because the game is in the a good position, and the masses are enjoying it- so there's nothing really 'wrong' to call out.
Man, I wish bugfixing was as simple as non-software devs seem to think it is.
Second year uni., computer science student here. Started my first project making an android notepad app, and even with like 500 lines of codes, I found it ridiculously difficult figuring out why the application kept randomly crashing. Truthfully I've gained a whole new level of sympathy for software developers (my future self included) 
So you want them to rush the patch process and possibly do more damage to the game then what is actually there? Anyone remember the emergency patch for 1.0.2 because there were issues in the patch?
If petitions like this actually did anything both Ubisoft and Bethesda would either release working games or gone out of business by now.
I admit, I'd pay for hair DLC...
I feel so ashamed.
Dont be. I would pay for a "different shades of your Inquisitor Pajamas" DLC.
Dont be. I would pay for a "different shades of your Inquisitor Pajamas" DLC.
If you play DA:I on a PC, the modders have succeeded in changing the Pajamas' colors.
http://www.nexusmods...geinquisition/?
Second year uni., computer science student here. Started my first project making an android notepad app, and even with like 500 lines of codes, I found it ridiculously difficult figuring out why the application kept randomly crashing. Truthfully I've gained a whole new level of sympathy for software developers (my future self included)
Yeah okay I will shake my fist furiously with my ten bucks safely tucked away. Hear that EA?
FEAR ME.
Yeah, that's right! We need a patch to fix... umm..
What exactly is broken? Don't get me wrong, there's several things in DA:I that I don't particularly like, but those were almost all conscious developer decisions, not bugs.
As games of this magnitude go... DA:I is pretty much bug-free as much as it can be.
Bring on the DLC!
I'm venturing slightly off-topic, but the topic is silly anyway, so here goes...
Android is one of the harder mobile platforms to develop for. It has what I like to call "Google syndrome", where they want you to write perfect code from the beginning (this happens with a lot of Google developer tools, unfortunately). If possible, iOS is a lot easier to get your feet wet on. It has a gentler difficulty ramp and it's an older SDK, so it's less of a pain to develop for. You don't have to create 15 xml files every time you change one thing.
(that said, I do prefer Androids for personal use)
Any advice on which programming language I should practice on? In college we mainly use C++, unless we get a project that demands otherwise- other than that I don't really practice coding that much, I was thinking of checking online contests on C++ and stuff and participating.
Any advice on which programming language I should practice on? In college we mainly use C++, unless we get a project that demands otherwise- other than that I don't really practice coding that much, I was thinking of checking online contests on C++ and stuff and participating.
C#
Yeah, that's right! We need a patch to fix... umm..
What exactly is broken? Don't get me wrong, there's several things in DA:I that I don't particularly like, but those were almost all conscious developer decisions, not bugs.
As games of this magnitude go... DA:I is pretty much bug-free as much as it can be.
Bring on the DLC!
If you are playing on the console I believe there are less problems, but there are still crashing issues with the PC version (its a lot more stable at least for me since launch), there are several abilities that don't completely function as described (such as Dispell not giving you a shield), or multi-player issues with not being able to progress to the next stage because the key doesn't drop.
I do agree especially with what we have been given and the continuing trend Dragon Age: Inquisition was really stable compared to many games launched over the last few years.
Can you define what you mean by 'Broken'. Are you saying that you cannot perform a specific function, or just that you personally do not like the fashion in which it works?
Good luck OP, PC controls are fine, need more ability slots and the hold command needs to work better but, not game breaking. Blak hair isn't black and, I'd like more hairstyles but, again nothing game breaking.
Man, I wish bugfixing was as simple as non-software devs seem to think it is.
Let's do some size comparisons, shall we? Rome II, a game from 2013, had 3 million lines of code. That's twice as many lines as there are words in the entire Song of Ice and Fire series of novels - and each line of a program contains multiple words.
Imagine editing an entire series of novels, but every time you touch a single word on this page, it could interact with words 1000 pages away.
Now additionally imagine that users aren't reading the actual text, they're reading a story generated by that text. So every time they encounter a bug, you have to first find where, in this giant stack of novels, there was a faulty instruction that caused the bug. Often it isn't a single instruction, but lines on different "pages" that, when taken together, cause problems. When you edit something on page 935 of book 3, you have to be reasonably sure it won't cause bad interactions with any other pages in any of the other novels.
So even if the source of the bug is easy to find, and even if it's easy to fix (and those are rarely true), a dev can't just make the edit and throw the update into the wild. The updates have to go through multiple rounds of quality assurance and certification, a process which takes weeks even for the kind of software I work on (which is much smaller than video games).
And even then, there will always be bugs. It's pretty much physically impossible to write software of that size without having bugs.
Heck, last I checked Dragon Age: Origins still crashes out mid-combat on multicore processors. That isn't surprising, since almost everyone had single core machines when it came out... and issues with multiple cores are often incredibly difficult to debug, especially if the software wasn't designed for multiple cores from the start. As a sidenote, this is how I know that many of the people nostalgic for Origins haven't played the damn game in years.
I keep hearing abilities are broken, but which ones? I haven't noticed any myself. Passives?
Yeah, that's right! We need a patch to fix... umm..
What exactly is broken? Don't get me wrong, there's several things in DA:I that I don't particularly like, but those were almost all conscious developer decisions, not bugs.
As games of this magnitude go... DA:I is pretty much bug-free as much as it can be.
Bring on the DLC!
Heck, last I checked Dragon Age: Origins still crashes out mid-combat on multicore processors. That isn't surprising, since almost everyone had single core machines when it came out... and issues with multiple cores are often incredibly difficult to debug, especially if the software wasn't designed for multiple cores from the start. As a sidenote, this is how I know that many of the people nostalgic for Origins haven't played the damn game in years.
Weird. I had a quad core when Origins was released, and after multiple playthroughs, I only ever had one CTD.
Incidentally, my last playthrough was less than a year ago, so my nostalgia is rather fresh
Yeah, but I just bought the ME trilogy and it turns out that the copies I bought don't come with any of the DLC. And I *really* want to find out what happens in the Lair of the Shadow Broker!
LOTSB and Citadel are the two best DLC in the entire franchise. From Ashes sucks but you get Javik, who adds a boatload of new content, including cutscenes that wouldn't be visible without him.
Man, I wish bugfixing was as simple as non-software devs seem to think it is.
Let's do some size comparisons, shall we? Rome II, a game from 2013, had 3 million lines of code. That's twice as many lines as there are words in the entire Song of Ice and Fire series of novels - and each line of a program contains multiple words.
Imagine editing an entire series of novels, but every time you touch a single word on this page, it could interact with words 1000 pages away.
Now additionally imagine that users aren't reading the actual text, they're reading a story generated by that text. So every time they encounter a bug, you have to first find where, in this giant stack of novels, there was a faulty instruction that caused the bug. Often it isn't a single instruction, but lines on different "pages" that, when taken together, cause problems. When you edit something on page 935 of book 3, you have to be reasonably sure it won't cause bad interactions with any other pages in any of the other novels.
So even if the source of the bug is easy to find, and even if it's easy to fix (and those are rarely true), a dev can't just make the edit and throw the update into the wild. The updates have to go through multiple rounds of quality assurance and certification, a process which takes weeks even for the kind of software I work on (which is much smaller than video games).
And even then, there will always be bugs. It's pretty much physically impossible to write software of that size without having bugs.
Heck, last I checked Dragon Age: Origins still crashes out mid-combat on multicore processors. That isn't surprising, since almost everyone had single core machines when it came out... and issues with multiple cores are often incredibly difficult to debug, especially if the software wasn't designed for multiple cores from the start. As a sidenote, this is how I know that many of the people nostalgic for Origins haven't played the damn game in years.
As a fellow software engineer, I wish I could give you 1000 likes for saying this.
Retour en haut
