Whoops....

[Anarkee]

So I'm taxiing around the runway after a training mission and I get to close to a personnel vehicle. I did not notice right away that two of my bottom rotor blades clipped the truck. The aircraft starts to shake a little then starts shaking and bouncing like crazy. At first I thought it was a bug or something, after switching to an external view I notice that two of my rotor blades are about 1 foot shorter than the others lol.

 

Looking closer I see debris from the rotors on the tarmac and also notice I have a flat tire as well. A piece from the rotor must of ricocheted off of the truck and blew out my left tire.

 

In this one its kinda hard to tell the tire is flat because some graphical artifacts showed up on the tire.....

 

Good shot of the rotors

 

 

Some artifacts showed up on the tire making it hard to see, this one still has the artifacts but i think you can see it's definitely flat lol.

 

 

I'm really enjoying this sim, all it needs now is DCS: Raptor F-22 expansion!! :pilotfly:

Edited August 26, 2009 by Anarkee
spelling

[topol-m]

Screenshots thread: http://forums.eagle.ru/showthread.php?t=32530&page=67

[Ovenmit]

Not graphical artifacts... that's pieces of rubber. Excellent damage model in this sim.

[EtherealN]

Also, those blades have been shortened by considerably more than a foot. In fact, you've lost nearly half of a ~7 metre blade. That is, those blades are about 12 feet shorter than they used to be. ;)

[Anarkee]

Yea they do seem to be allot shorter than a foot ....

 

The attention to detail is just amazing, even down to actual pieces of the broken blades on the runway. Don't think I've seen damage modeling like this in any type of sim before. IL2 has some impressive damage modeling, , especially with the losing parts of your wing or motor oil painting the inside of your cockpit, but still not as good as DCS. Also the software runs great, really smooth fps, no crashing that I have experienced yet.

[joey45]

apart from pilot error.

[Waldo_II]

Did you try taking off after taking those pictures? The torquing effect will spin you around and around. I've done it a few times, plenty of fun.

[Speed_2]

Why does nearly everyone assume it's a bug when something goes wrong in the chopper and they have no clue what caused it? I have been guilty of it myself from time to time.

 

That said, there STILL are quite a few bugs, especially in multiplayer... about a fifth of my flights end in freezes or crashes (of the computer kind). :( This is still alot better than before I figured out that I can only play missions created after 1.0.1!

[sobek]

Why does nearly everyone assume it's a bug when something goes wrong in the chopper and they have no clue what caused it? I have been guilty of it myself from time to time.

 

That said, there STILL are quite a few bugs, especially in multiplayer... about a fifth of my flights end in freezes or crashes (of the computer kind). :( This is still alot better than before I figured out that I can only play missions created after 1.0.1!

 

Just guessing here but statistically it is more likely that theres something wrong with your computer than the freezes actually being a result of the game. :music_whistling:

[159th_Viper]

Why does nearly everyone assume it's a bug when something goes wrong in the chopper and they have no clue what caused it?

 

Indeed............

 

..........................

 

 

That said, there STILL are quite a few bugs, especially in multiplayer... about a fifth of my flights end in freezes or crashes (of the computer kind). !

 

Lol - Tickles me Pink that you have just perpetuated the very behaviour you call into question.......:thumbup:

 

 

 

Why do you assume your Freezes or Crashes are Bugs?

[Speed_2]

Indeed............

 

..........................

 

 

 

Lol - Tickles me Pink that you have just perpetuated the very behaviour you call into question.......:thumbup:

 

 

 

Why do you assume your Freezes or Crashes are Bugs?

 

Just guessing here but statistically it is more likely that theres something wrong with your computer than the freezes actually being a result of the game. :music_whistling: [/Quote]

 

Right... because the seven people in our squadron who now have Black Shark in my Falcon 4 squadron ALL find the game unstable in multiplayer- let's shove the blame off the developers and put it on the customers!

 

I am very satisfied with this product, as it's not anywhere near unstable enough to be unplayable or anything like that, but don't be an ED fanboi and try to pretend like there's NOTHING wrong.

[159th_Viper]

 

It's not very unstable or unplayable or anything even close to that, but don't be an ED fanboi and try to pretend like there's NOTHING wrong.

 

Rather than shooting your Mouth Off stating that the SIM is buggy, post something constructive and elaborate as to what Bugs, in your opinion, are present. In addition, what behaviour is experienced by yourself and your squaddies that lead you to the conclusion that the Multiplayer aspect is 'Buggy'.

 

And Yeah - think twice before you personalize a post and call me an ED fanboi in future.......You will get stepped on ;). Keep posts objective - nothing constructive can come from subjective attacks :)

[EtherealN]

What hea means is that there's most likely tonnes of other things that are common to all your squad's computers. That is why an error being reproducible is the big piece of gold in troubleshooting and identifying bugs - because it might be a bug in a network driver that you all happen to use, or a graphics driver you all use, or practically anything like that.

 

That is the point. Until the issue is properly isolated and made reproducible, the list of suspects doesn't end with the application. Everything on the computer would be suspect. Of course, the application running is one of the chief suspects (but note that your machines will have at least several dozen processes running that might cause issues), but to say with certainty that the issue lies in DCS is to commit the same error as someone who would say with certainty that it is not in DCS. (Which no-one has said here.)

 

An example: there was a guy who was absolutely furious that the simulator kept crashing. It was then isolated to him using the Sidewinder mouse by microsoft. So he was angry that ED were such "amateurs" that they didn't make their stuff compatible with "high-performance" mice. (I disagree on that judgement of the Sidewinder mouse though, but that's not the point.) Then, when the issue has been properly reproduced and tested and examined, the bombshell arrives: there is nothing ED can do about it, because it is the mouse that is incompatible not with DCS, but with certain parts of DirectInput. All they could do was contact Microsoft, highlight the issues and hope that Microsoft fixes either DirectInput or the Sidewinder mouse.

 

And there's been a lot of errors reported where, eventually, DCS is not the culprit, but rather some other unfortunate bit of the computer that just happened to get in the way for DCS specifically.

[Speed_2]

Rather than shooting your Mouth Off stating that the SIM is buggy, post something constructive and elaborate as to what Bugs, in your opinion, are present. In addition, what behaviour is experienced by yourself and your squaddies that lead you to the conclusion that the Multiplayer aspect is 'Buggy'.

 

And Yeah - think twice before you personalize a post and call me an ED fanboi in future.......You will get stepped on ;). Keep posts objective - nothing constructive can come from subjective attacks :)

 

Lol... and YOUR post wasn't intended to be offensive towards me?! Sorry, but I generally reply with anger when someone purposely offends me or insults my intelligence...

Edited August 30, 2009 by Speed_2

[Speed_2]

What hea means is that there's most likely tonnes of other things that are common to all your squad's computers. That is why an error being reproducible is the big piece of gold in troubleshooting and identifying bugs - because it might be a bug in a network driver that you all happen to use, or a graphics driver you all use, or practically anything like that.

 

That is the point. Until the issue is properly isolated and made reproducible, the list of suspects doesn't end with the application. Everything on the computer would be suspect. Of course, the application running is one of the chief suspects (but note that your machines will have at least several dozen processes running that might cause issues), but to say with certainty that the issue lies in DCS is to commit the same error as someone who would say with certainty that it is not in DCS. (Which no-one has said here.)

 

An example: there was a guy who was absolutely furious that the simulator kept crashing. It was then isolated to him using the Sidewinder mouse by microsoft. So he was angry that ED were such "amateurs" that they didn't make their stuff compatible with "high-performance" mice. (I disagree on that judgement of the Sidewinder mouse though, but that's not the point.) Then, when the issue has been properly reproduced and tested and examined, the bombshell arrives: there is nothing ED can do about it, because it is the mouse that is incompatible not with DCS, but with certain parts of DirectInput. All they could do was contact Microsoft, highlight the issues and hope that Microsoft fixes either DirectInput or the Sidewinder mouse.

 

And there's been a lot of errors reported where, eventually, DCS is not the culprit, but rather some other unfortunate bit of the computer that just happened to get in the way for DCS specifically.

 

Ah, I get what you are saying. The bugs we experience are likely partly caused by other programs, but not all of them, as we have some of the same issues and wildly different machines. Probably discussing this more would just get this thread even more off-topic.

Edited August 30, 2009 by Speed_2

[159th_Viper]

......Sorry.....

 

Accepted ;)

 

Now, are you going to inform us as to the 'Bugs' that you are experiencing so that we can attempt to isolate the issue and troubleshoot on your behalf?

[Anarkee]

I didnt try taking off after it happend that time, but I've clipped the rotor blades on a few things since then (like the ground :megalol:). That was pretty crazy.

 

I read somewhere, a good while before DCS was released, that the rotor blades can actually flex far enough to make contact with each other and possibly cause them to break in certain situations.

 

Anyone had that happen?

 

As far as bugs go, I still have not had any problems. I even have a Sidewinder X8. I have only spent a little time in multi-player, and only with 2 people, we had some connection issues at first but unlocking ports fixed it.

 

I'm definitely familiar with the DirectInput bug though, had "DINPUT8.DLL" crash on a few other games, it seems to me it might be caused by using a Sidewinder and Logitech G14 keyboard together.