viper2097 Posted August 26, 2019 Posted August 26, 2019 Psssst, don't say anything bad about Razbam because of their "not user orientated behavor". Their Fanbois will wake up, crush you and all comments will be deleted because of "off topic". Steam user - Youtube I am for quality over quantity in DCS modules
SGT Coyle Posted August 31, 2019 Posted August 31, 2019 Bumping this thread (and reporting Harrier bugs in general) is a bit like playing the lottery, because why not? Once in a while, you put 5$ in and who knows, maybe this time you get lucky! On that note, BUMP! This is a bug and it is not solved. You're not supposed to COMMENT IN THIS SECTION!!! Just re-report the bug. Send =Decoy= a PM about it. Night Ops in the Harrier IYAOYAS
bkthunder Posted September 7, 2019 Posted September 7, 2019 You're not supposed to COMMENT IN THIS SECTION!!! Just re-report the bug. Send =Decoy= a PM about it. I guess this was not supposed to be moved to the "resolved bugs" section, since it obviously isn't resolved (along with a number of other bug reports...), hence the comments :music_whistling: Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s
LastRifleRound Posted September 10, 2019 Posted September 10, 2019 You're not supposed to COMMENT IN THIS SECTION!!! Just re-report the bug. Send =Decoy= a PM about it. You're not supposed to MOVE UNRESOLVED BUGS TO THIS SECTION!!!! :megalol:
viper2097 Posted January 15, 2020 Posted January 15, 2020 Unfortunately, it is still not touched yet. Decoy, didn't you promised to correct all threads who are are, but are still not resolved? Steam user - Youtube I am for quality over quantity in DCS modules
sc_neo Posted January 16, 2020 Posted January 16, 2020 Yep he stated he wanted to move all bug reports back to the unresolved section that were wrongly placed here by the "other dude".
bkthunder Posted April 15, 2020 Posted April 15, 2020 [ADDED TO COMMUNITY BUG TRACKER] https://docs.google.com/spreadsheets/d/1gYpmYD4VVaTn1YkHd_K7CJxOysoOqdN-K5oZs_anX7c/edit?usp=sharing Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s
Swift. Posted June 4, 2020 Posted June 4, 2020 Is this still bugged? I do not believe so. My deleted message above was because I wrongly bumped this thread before realising it had been fixed a while ago. 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
amalahama Posted June 4, 2020 Posted June 4, 2020 Cool, it's one of those bugs that put me out of my nerves
Holbeach Posted June 4, 2020 Posted June 4, 2020 The FPM and GFPM are now in their correct horizontal plane. BUT. During a level turn, they are either above or below the horizon, depending on which side the wind is coming from, whilst still displaying 0 fpm. Only when the wind is either fore or aft, do they sit together on the horizon. .. ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals. ..
amalahama Posted June 4, 2020 Posted June 4, 2020 The FPM and GFPM are now in their correct horizontal plane. BUT. During a level turn, they are either above or below the horizon, depending on which side the wind is coming from, whilst still displaying 0 fpm. Only when the wind is either fore or aft, do they sit together on the horizon. .. So still it's bugged. What a surprise
Holbeach Posted June 4, 2020 Posted June 4, 2020 It seems that way. If you manually turn, with the FPM on the horizon, you will be in a descent and at low level will be very dangerous, especially at night. You can rely on the FPM, when there is no wind. BTW, It's completely different to the OP picture. .. ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals. ..
amalahama Posted June 5, 2020 Posted June 5, 2020 If you manually turn, with the FPM on the horizon, you will be in a descent and at low level will be very dangerous, especially at night. That's absolutely not how it should work. Both GFPM and FPM should provide correct vertical indication, the only difference being the beta factor. Watch this video
bkthunder Posted June 5, 2020 Posted June 5, 2020 So this has been moved to the "resolved bugs section". Can anyone confirm it's actually fixed? If so I'll mark it as fixed in the community bug tracker. Thanks Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s
Marsvinet Posted June 6, 2020 Posted June 6, 2020 The original bug is fixed, where the vector representations were fixed to each other in the wrong way. Now it is partially fixed. Instead it only starts to show funky things at high bank angles. So, yes, the bug of this report is fixed. But it is still not fully correct.
Holbeach Posted June 6, 2020 Posted June 6, 2020 So this has been moved to the "resolved bugs section". Can anyone confirm it's actually fixed? If so I'll mark it as fixed in the community bug tracker. Thanks It's an evolved bug. Not the same as the original, but wrong in a different way, like a mutation. It is incorrect at any bank angle, when a side wind is involved. .. ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals. ..
amalahama Posted June 6, 2020 Posted June 6, 2020 Yeah you name it. In summary: still open and not resolved
vctpil Posted June 6, 2020 Posted June 6, 2020 The problem is not really linked to the ghost vector now, but about the fact that the aircraft roll around the ghost vector axis instead of its longitudinal axis. The aircraft is then unflyable with wind. IAMD Ryzen 9 5900X 12x 3.7 to 4.8Ghz - 32Go DDR4 3600Mhz - GeForce RTX 3080 - Samsung Odyssey G7 QLED - AIMXY
Recommended Posts