Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: HawkerMKII on July 30, 2002, 07:20:41 AM
-
I know HT and his staff work really hard to fix the problems in AH, but this lock up thing is a joke:( . In 1.09 the only peoblem I had was the crash lock in the F-4's sooooooooo guess what, I never flew them:) . Also I was able to play a hour or longer each day with 1.09, 1.10 I maybe able to play an hour a week. Our money should not be spent to be the bug testers for this game, so come on HT talk to us, fix the problem or lets go back to 1.09 so we can play and you can fix the bugs in 1.10:) I know some of you will tell me to try this or try that.......I had a friend come over this last weekend and he is a puter wiz, worked on my puter for 6 hours and said he could not find nothing wrong. Help us HT so we can get back to having fun in AH.
Thank You
HawkerI
9 Giap
-
Why don't you update to 1.11 same as the rest of us?
-
HT and Pyro(and staff) have been working in the online flight sim industry since 1994-95. I assure you that they've run into bugs such as this in the past, and squashed them.
If you've ever been in software business where your job is to find bugs and try to reproduce them in order to narrow down where to look in the code..its very difficult. I do this on a daily basis with a software tool that built the aircraft you fly on when you visit your mother or go on vacation. The toughest part is trying to reproduce this in a consistent manner in order to narrow down the area which is causing the anomoly. Its a thankless job, and it gets one very frustrated at times. Give HT and company time, they'll find it. You never go back a version in software, you always move ahead and squish the little bugs as they arise.
Have patience.
-
well said Rip
-
If you've ever been in software business where your job is to find bugs and try to reproduce them in order to narrow down where to look in the code..its very difficult. I do this on a daily basis with a software tool that built the aircraft you fly on when you visit your mother or go on vacation. The toughest part is trying to reproduce this in a consistent manner in order to narrow down the area which is causing the anomoly. Its a thankless job, and it gets one very frustrated at times.
Hey Rip, I didn't know you did testing and debugging, that's what I do for big blue. We now have at least two things in common! ;)
But Rip is correct, finding software bugs is difficult, painstaking work. I have faith that HiTech and Ronni are doing everything they can do isolate the problem.
-
Well, its alot less glamourous than my previous job (NC Programming and Design) but it pays better since its a tedious job! We also get to test the latest and greatest in CAD/CAM software before the public sees it. The biggest pain is assisting engineers (in an active "production" application CAD/CAM product) that *think* they know EVERYTHING, its our job to patiently assist them in removing their heads out of their asses. ;)
-
You hit it right on the head, Rip.
With the Nav program we make, I'm the guy with 4 systems (Windows 2000, Windows XP Pro, Windows 98, Windows NT 4) who tries to duplicate and hunt down the error messages customers report. Its a lotta work and when you do find the critter, its largely a thankless job ("You should've found it in the first place before releasing").
Bugs, err, "undocumented features" happen. Its one thing when a program is in beta under 10 or so systems. But release it to a few thousand and then that's when it gets interesting!
-
Originally posted by Ripsnort
I do this on a daily basis with a software tool that built the aircraft you fly on when you visit your mother or go on vacation.
Thanks, Rip. Now when they send me to Malaysia to set up the office I have to take a boat. You're a BIG help, buddy!
:D
By the way, it saves time if you just sever the neck. The head is usually spring loaded and will just return as soon as you walk out of the room. A friendly bit of advice from someone who's been trying with minimal success to educate lusers for over 20 years now.
-
Originally posted by Puck
Thanks, Rip. Now when they send me to Malaysia to set up the office I have to take a boat. You're a BIG help, buddy!
:D
By the way, it saves time if you just sever the neck. The head is usually spring loaded and will just return as soon as you walk out of the room. A friendly bit of advice from someone who's been trying with minimal success to educate lusers for over 20 years now.
Rest assured, when I was a designer, it was in tooling. Today, I just assist the engineers with the software when they get stuck, not the design phase! :p
-
while the cdt bug sucks..we can be assured that the problem is being fixed, they always are..last major update a lot of people had bad frame rates, me included, i got really fed up, but the the prob was fixed after about 3 weeks. which is about the time it has taken to fix most of the major bugs we've had..
wait it will be fixed...(fingers crossed):)
-
Originally posted by Ripsnort I do this on a daily basis with a software tool that built the aircraft you fly on when you visit your mother or go on vacation.
I feel safer know.......no, not realy.:p
-
Hey banana ... I work for Big Blue in Southbury !!!
I am a software architect for a large enterprise expense reporting solution and we can QA until we are blue in the face (no pun intended) and squash any and all bugs ... BUT ... release the software to 1000s of people and they will really test the boundries of your logic and code that you never even considered. It is just a fact and reality in the software world. We never go BACK ... always forward.
Patience .. HT and crew will squash this !!!
With everything that I have read, I am betting on the Bomber Formations as the culprit here. Especially when they are blowing up from either gun fire and/or when the "life cord" is broken.
EDIT:
Originally posted by hitech
Progress on the lockups, It's not fixed yet , but managed to have it happen while in a debug session. Narrowed it down to an out of range Attitude in the drone system. My guess is it happens when a formation first comes into view.
Was here tell 7:30 last night looking at the debug session, was planing on continueing this morning, but the storm/power killed the debug session.
We got that little bugger corrnered, now to get out the 30 foot fly swater.
BINGO !!! HT has this one in his grasp and will choke the life out it !!! :D
-
They could rerun last Sunday's snapshot and monitor it. The freeze bug will rear it's head again and maybe they could track it down? Would sure be a great acid test once a proposed fix is ready.
-
nice answer RIP
Hey Rip i do sorta the same assisting engineers with CAD TOPO
etc...Teramodel type stuff... are you familiar with this?!
Sorry about the off topic... throw rocks at me if you want...
T0J0
-
mine always seems to freeze when a formation of bombers is nearby, and seeing as how HTC made a change to the appearence of formations and the UDP setup shouldnt it follow that the problem lies in that area?
my bet is it is.I too have only noticed this sort of thing since 1.11 and i have also had the most discos in a single tour than ive had in over 2 years (some 22!).HTC needs to address this problem a little quicker this time i think.Ive logged off in frustration more times than i care to remember this tour and im in the 'principle' mindset at the moment.I only hope i can control it so i dont quit ;)
-
Rip
Great reply, always like the bug reports that say
this function does not work fix it. but have no description of the failure, when it occurred, where on a map one was, altitude of plane, what you were doing, banking, turning, dive or climb.
Testing can only find and fix so many problem, take a product that looks like it is complete and give it to 10,000 people runing on a number of difference operation systems. 95, 98, 2000, ME, XP home, XP Professional, etc. On a series of CPU running anywhere from 333 mhz to 2gig plus, with
various motherboards and configuration. Now add in the internet and communication problems to the mix and it gets more difficult to complete test every possilbe combination that will exist in the field.
Software is never fully tested no matter how long you test until after it is in the field. Then the real testing begins.
I know all about this, Developer, and change team
It is interesting when you find a bug that was in the code for a number of years and it just showed up 10 or 12 years later.
DarkHawk