Jump to content

jaylw314

Members
  • Posts

    1052
  • Joined

  • Last visited

Everything posted by jaylw314

  1. Wait, that is odd, I use a Reverb G2 as well, and it's definitely not like that. The vertical FOV of the G2 is less than 90 degrees, so the center of your IHADSS is more than 1/3 of the way to the top edge?? I'd suggest grabbing a screenshot with the IHADSS monocle visible. The visible monocle can give a better perspective as to how off-center it is in the FOV, since it covers a far larger area than the symbology EDIT: OK, thinking about it more, I think what your saying is that the Reverb G2's FOV when your head is level covers more above the horizon than below? That does seem to be the case (I recall the Odyssey+ was much better in this regard), but right now the symbology for me seems to be in the center of the FOV, which, with head level, is actually above the horizon. The downside to moving the IHADSS down in the FOV is that the lower part would then be significantly out of the lens sweet spot
  2. A couple points to bear in mind (and just to beat a couple dead horses too): The HUD was designed to be visible across two eyes, so, unfortunately, that means if you're not playing in VR, you might see less of the HUD, hence having to move the viewpoint a little forwards The little bump at the bottom of the HUD is the video camera (non functional in DCS) The default seat view that ED intends has the HUD top edge about 5 degrees below the horizon on the ground, and the boresight circle just barely not visible without moving your head. A lot of people complain this is unrealistic, and a lot of people claim this is realistic. In ground attack, your priority is looking down and over the nose rather than up, so I just go with it Ah, and @Hiob mentioned adjusting zoom--you actually want to adjust your head position forwards, IIRC that's RSHFT+RCTRL+Numpad / That makes the HUD frame bigger in comparison to the HUD display. Zooming in will make both bigger by the same proportion, but the HUD display will remain cut off by the HUD frame Edit: Oops, no @Hiob got it right, I didn't read his whole post
  3. Haven't tried vehicles over all ground textures yet, but last night it did look a little better. Hopefully, people will chime in as they get experiences in multiple settings.
  4. Hmmm, ATFLIR is an F/A-18C thing, are you in the right forum? A-10C can only use Litening TGP How are you getting your buddy to lase from a Reaper drone? Or are you talking about the AI JTAC? If it's the AI JTAC, does that work through a drone? I have to admit, I've never tested it. Have you been successful conducting an LGB attack with a drone JTAC from the Harrier? If not, there's a whole palaver you need to go through with the AI JTAC to get them to turn on the laser. One common "doh!" mistake in LGB attacks in the A-10C is forgetting to make the TGP SPI. The CCRP cueing guides you to the current SPI, and if it's still set to a steerpoint somewhere other than where your TGP is looking, you won't get the fall line or other guidance symbology. Remember, your only indication of your SPI sensor is the data block in the lower left of the HUD.
  5. When placing units, it can be a bear to figure out which can actually see each other due to terrain. I know the map depicts elevation and you can see the numeric for elevation at the cursor, but that lacks the "big picture" in terms of figuring out who has the high ground. It's tough to place units behind a ridgeline and then come rolling over when you can't figure out where the ridgeline is.
      • 1
      • Like
  6. FYI, you'll probably do better posting any questions in this part of the forum: https://forum.dcs.world/forum/909-a-10c-iron-flag-part-i-campaign/
  7. When in distress, you press ESC
  8. If you're going to use CCRP mode, it would make sense to make HUD SPI and use the TDC (or the HMD SPI and the HDC) instead of using the TGP. That way, you're looking at the "big picture" instead of looking through a straw. Again, if you do a relatively low (3000' AGL) level drop, you don't really need to lead moving targets much more than you would have to lead them in CCIP anyways. Neither are particularly helpful if you're at a higher altitude, though Edit: Duh, forgot you can also use CCIP in delayed release mode
  9. It's there and working, it's just REALLY hard to see under typical room conditions. In VR with an Odyssey+, which uses OLED's, I preferred night AAR with no NVG's because the nose lighting seemed adequate. In the G2, which uses backlit LED's, it's almost impossible without NVG's. In any case, I thought I recalled reading in the flight manual that NVG's were allowed in all phases if the tanker lights were compatible
  10. Going as fast as possible helps to get the CCIP pipper in the HUD, too. Things that help: Low altitude Steep dive High speed Obviously, all 3 at the same time is not good for your health, but you can just get it in view in level flight at full throttle about 2000' AGL
  11. Either that, or you can get REALLY close and just use the TLAR method (That Looks About Right)
  12. Hah, yes I am but I'm still working on the taking-off-without-crashing part, haven't come close to TADS yet
  13. I've found I had to massively mess around with the gains and levels to get vehicles and people to show up in IR, so mess around with them. Sadly, there's not a specific number to set them to, because it seems to depend on the terrain, clouds, lighting and distance. There are some instances where it's just basically impossible--ironically, vehicles out in the open on grassy terrain seems to be the worst for me.
  14. Is it something MP related? I don't recall seeing it in SP, but did in MP. I wonder if it's related to the cloud shaking bug from the original 2.7 update, this seems to be a similar quality of wobbling...
  15. Yes, but at least there's a workaround since who knows how long a fix will take?
  16. Does the Boat Switch not change the color of the MAV page crosshair and symbology from white to black?
  17. Pedantic alert! AFAIK you ALWAYS truncate or round down if you drop digits, so GG 32328 36131 would be entered as GG 3232 3613. Not all map grids are the full 100,000m^2, so in theory, if you round up, you might have a grid reference that doesn't exist, and should actually should be in the adjacent grid. Therefore, the standard practice is to always drop the unused digits. Obviously this is pretty rarely an issue, hence the pendantic-ness
  18. Haven't tested it yet, but from what I understand, the new belief is that tanker TACAN's use ground T/R mode, not A/A TR mode. Other aircraft use A/A TACAN, but I don't think any current modules have the DME transmitting equipment, so A/A TR mode is pretty much pointless. Hopefully, this means tankers should have the TACAN and distance info in ground T/R mode, but I haven't confirmed this myself yet
  19. The bug is less that the MFCD's are too bright--it's more so that the BRT +/- rocker does not affect the backlight brightness at all, as it should and used to.
  20. The Maverick IR and EO seekers have much lower resolution than the TGP camera, so in cluttered areas, it can fail to lock or lock on the wrong pixel if you're more than 5 nm away.
  21. AFAIK, no. Landing and repair does not fix it, you need a new plane
  22. Ooof, you are correct, I forgot you can change the FP waypoint attributes in the FP menu itself Don't listen to me, listen to @Frederf
  23. I think I know what you're asking, but correct me if I'm wrong. Are you asking why the NAV--> ATTRIBUTES page still says TO FROM even though the STEER PT knob on the AAP is set to FLT PLAN? AFAIK, the NAV-->ATTRIBUTES page allows you to set the default waypoint attributes when you create a new waypoint. The fact that is says TO FROM simply means that if you create a new waypoint, it will create the next new waypoint with the enroute steering attribute set to TO FROM. To see or change the actual steering attribute for an existing waypoint, you have to look at the existing waypoint, like in the WP MENU-->WAYPT page. However, when you turn the STEER PT knob to FLT PLAN, the HSI automatically goes into TO TO steering mode and overrides the existing waypoint's attributes (without changing them), so if you look at the WAYPT page, it will still show its existing attributes (TO FROM, in the case of the video above) TL;DR -- When you turn the STEER PT knob to FLT PLAN, it is always in TO TO mode and any existing steering attributes are ignored.
  24. LOL Polarized sunglasses aren't terribly expensive, although nowadays most cheapo sunglasses are plastic. I don't know that multiple polarizing filters make things better, because the LCD still gets completely blocked at multiple angles.
×
×
  • Create New...