Jump to content

Giskvoosk

Members
  • Posts

    69
  • Joined

  • Last visited

1 Follower

About Giskvoosk

  • Birthday 03/04/1879

Personal Information

  • Flight Simulators
    Top Gun NES
  • Location
    Antarctica
  • Interests
    Antarctica

Recent Profile Visitors

1875 profile views
  1. To further demonstrate the problems i described, not that many people care, i'd like to share a few video clips since game built 2.8. I assume the content-aware auto gain mechanism is based off what's present in current FoV regardless if the camera is facing strong light source or not. Lets say you are more likely to be flashbanged in a pit covered in darker tone, if the darker portion of the cockpit remains in your FoV. Scenario 1: Partially overcast, flak burst from merely a couple miles away blends into the background unless camera FoV is purposefully zoomed into the area. The gain turns down itself soon as I orient away from the forward, of which comprises cockpit structures in darker tone. Scenario 2: drastically overexposed in cockpit view compared with in external against same piece background in distance. Hardly can be described as usable in 1.6 gamma, let alone default setting of 2.2. Scenario 3: gain appears to be normal-ish when FoV oriented away from darker cockpit structure while facing same piece of external background. In conclusion the dynamic range has been seriously compromised since 2.8, in current form it might appeal more to sunset screenshot enthusiasts who are clueless about how-to's in Adobe Camera Raw / Photoshop. The one in 2.7 at least didn't have quirkiness in this regard. The quicker solution if I would suggest is to revert back to the older lighting or provide an option to turn this new feature off, now that few cares it appears to be a moot point at this moment. One can only wish it could be tuned to somewhere usable someday in the future.
  2. It's quite confusing which exactly is the upper limit when there's conflict in the same paragraph for A-10C w/ and w/o expansion. I haven't been actively playing with the new C but I distinctively remember 17XX being available beforehand because I was regularly using laser codes of this range to deconflict. Now just been from a quick in-game test, it seems that 1688 has also been applied to non expanded C as the upper limit, for LSS, designation, and the DSMS store page. And what baffles me is for designation and bomb code it might be attributed to hardware limitation, but why the same is applied to LSS mode as well? Other Litening-equipped aircraft do not have such restriction. It would be appreciated if devs could talk us through the changes and the reasons behind.
  3. Thanks for verifying! F-5 has so few means of radio navigation, at this point all hampered due to this bug. Hope it could be addressed before Christmas otherwise it will be a long haul.
  4. Did a follow-up test. It appears to be HSI bearing pointer that is in fact bugged, the pointer stays stationary in ADF mode as well.
  5. Can confirm the same problem here. Devs please recognize and fix the bug as soon as possible, thanks.
  6. in that case, expanding the line to the following will allow you to remove the smudginess and all baked in reflection
  7. This serves as scratch removal as well.
  8. Thing is, TACAN on US combat jets from 60s and in some case early 70s often had their air to air mode marked as A/A only like on F1, no differentiating between Receive only and T/R but was functioning like the latter, as this can be observed in flight manuals from that period. Given that a rotating antenna was required for bearing information and wasn't widely available at all back then, the primary usage of A/A was for ranging-only TACAN yardstick. Hence i mentioned in original post that ranging was more of a primitive function in this mode. It would be counter-productive if its modelled the other way around. Not true, most (if not all) TACAN-equipped module (i don't own jf-17/c-101/mb339 so cannot tell these 3) can perform fighter-to-fighter TACAN yardstick just fine, while F1 can't. It's little bit finicky for F/A-18 since more than half of its channels have been occupied by MIDS but the rest are doing well. AI tanker is another touchy subject let's just ignore this for now. They're operating on non-A/A mode and behave like an airborne mobile ground station. For whatever reason F1 can receive the bearing in A/A, but not in any other jets.
  9. The issue remains unaddressed in 2.8.0.33006 Bump
  10. I don't think that's the case here, considering there's no difference between F1AZ/CZ's manual regarding A/A TACAN. There's no mentioning that A/A mode are exclusive to AAR-capable jets only. And as for now A/A mode is available, just lacking the capability of distance measuring.
  11. Update: the problem is not fixed as of DCS 2.8.0.33006 Tested with tanker aircraft, the larger arrow was pointing correctly to the tanker however cannot tell the range to it.
  12. New feature, handling graphics in an inelegant way unfortunately. Like some sort of ill-tuned HDR. Also it appears to be automatically compensating for a higher gain in the cockpit when camera facing 11~1 o'clock and 5~7 o'clock which doesn't make much sense. Despite the fact that industry standard for gamma is ~2.2, at this setting its like being flashbanged when facing forward in the cockpit view.
  13. As the title suggests, slant range reading is not available when contacting other airborne tacan transmitter, neither from tanker nor on either end of tacan yardstick. If anything, i thought ranging was more of a primitive function than bearing-interpreting in A/A operation?
  14. Now that the new 3D model has been updated, so far changes are as follows #985: dorsal fin #986: countermeasure pods, and the corresponding control box behind ejection seat #987: nose cone and refueling probe #988: antennas on vertical stab #989: some venting port on fuselage aft section #990: wingtip lights #991: undernose recon camera, and different arrangement for lights and antenna on the spine #992: 2 or 3 mirrors on the canopy bar #993: different arrangement for bort code on fuselage aft section
  15. No arguments #985~993 exist at this moment, nor has any of the external models been updated in Friday's patch. Chances are they were missed out in the compiling phase. Let's wait and see in the next update.
×
×
  • Create New...