Jump to content

Hog_No32

Members
  • Posts

    484
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    nowadays nothing but DCS
  • Location
    near CAOC Uedem

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. same here, Blade seems to hit something with his left wing as soon as he starts taxiing on deck. I tried it 3 times and it‘s always the same. His left wing emits smoke and the LEF is missing. He taxies to the CAT nevertheless but at the end of the cat stroke (i.e. at the bow) he explodes. No wingman on that mission. I noted that the OB changelog in fact mention that ground crew was moved to prevent Blade from running over them. It seems whatever that change was it made things much worse:( I‘ll have a look at the mission in the ME tonight to see if I can find what might cause the apparent collision of Blade‘s jet upon taxi.
  2. Thanks Bunny Clark. I'll try to engage the F-5s while on takeoff next time...that way I have a fair chance... LOL. And then I hope I can deal with what will come thereafter.
  3. Love this campaign but I need some advice for how to get through M11. I have no problem destroying the SA-6 radar, either the HARM does the job or the CBUs. But I have big trouble fighting the enemy fighters that party seem to pop up 5nm from me out of nowhere. The main problem really is that I cannot spot the enemies visually or at least not fast enough. Even though I get a spike on my RWR (and that replicated on the JHMCS which is a huge help generally) and try to start my visual scan from there, at this point they are usually already pointing their tiny noses in my direction (the F-5 that is) and I get heaters lobbed my way. I mean, I am absolutely conscious of the fact that I am really not the greatest dogfighter, but I usually get the stuff done after a couple of tries. But I can‘t progress from M11 onwards... Any ideas?
  4. Thanks for the update and your continued support!
  5. Awesome, I enjoy this campaign very much! What I love the most? -the rather realistic scenario -well built missions, immersive, challenging at times but very enjoyable -good briefing material -placement of SAMs at real-world locations -continued and tireless support including updates -voiceovers ...that‘s quite the pedigree for an outstanding DCS campaign! Thanks for your great work, Bunny Clark.
  6. Again, many thanks. You are making valid points and I‘m sure I‘d love the map. I guess at this point it is more a „when“ rather than an „if“ I will purchase it-question. Even if it won‘t run too well on my Hornet in a demanding mission, I will take out the Gazelle and just enjoy the scenery in some low level hops.This business is so small that I am usually inclined to rather purchase modules/campaigns/terrains than not, even if it may not be a piece I expect to heavily employ. As long as I see a little bit of value or frankly fun in something or my learning curves become too flat with other modules I want to support the ED and the 3rd party devs. That is, of course, as far as my financial situation allows it. Editorial note: feel free to replace ‚financial situation‘ by ‚wife‘... Happy flying Ziptie! Cheers, Hog No32
  7. Thanks Ziptie for your extensive response. Yes, I use a 2-monitor setup with a combined resolution of 3360x1440. I am sure VR would kill my rig...:-) Re the second point, I think I could have explained this better: What I want the carrier to be is as far AWAY from the shore as possible. I think that is more realistic and I do like longer missions. From what I could guesstimate based on screenshots of the current state of the map is that its western boundary is max 80-90nm from the Israeli/Lebanese/Syrian shore. I don’t think that a carrier group would want to be so close to Indian country and potentially within range of land-based anti-ship missiles. So I am looking forward to „more water“ in the west of the map to place the carrier there Cheers
  8. Thanks LooseSeal for that input. I am as well on the verge of buying Syria but I hestitate mostly because of performance concerns. I have a really old rig (i7 870, 2.93GHz) which has seen only little upgrades over the years (16GB DDR3-1333, SSD and a Gainward GTX 680 with 2GB). It runs ok on PG, Caucasus and NTTR with modest settings. But I fear with all the eye-candy of the Syrian map it will be underperforming significantly... 2nd point for me is I will definitely wait until the expansion with Cyprus comes out. Not because of Cyprus itself but because it will allow me to place a Supercarrier at a more reasonable (i.e. realistic) distance from the shore. Since SC came out I rarely operate my Hornet out of land bases...
  9. Totally unrealistic! I can confirm that in the REAL ME the icon doesn‘t look that way! Huge immersion breaker, akhope we‘ll get a hotfix soon... Lol, just kidding. And absolutely no offense, Tholozor. Everybody knows you are an outstanding contributor to our community for sure. And I’ve noticed the icon issue too and do appreciate if the team will fix this eventually.
  10. I guess the answer is: Not at all. The (night) lighting is part of the scenery and cannot be switched on or off, neither generally nor locally on any given map. It is simply „controlled“ by the time of day. I like the idea though. It would be extremely cool if the city lighting could also be linked to the damage status of nearby power stations or even powerlines! My workaround: When I go on a big night strike I always imagine it to be night 1 of the conflict, Task Force Normandy did its job and the enemy doesn‘t expect me coming. Baghdad was still fully lit when the first 2000-pounders came down in January 1991
  11. Actually the same behavior can be observed even WHEN using TrackIR :smilewink: When I have to look at an object that is exactly on my 9 o‘clock with TrackIR, I don‘t turn my head so much that I have the 9 o‘clock position in the center of my view because my eyes will already have moved to the left edge of the screen. The center of my FOV is probably at the 10 or 10.30. The same happens when I look inside for a switch deep down in the cockpit.
  12. Ok, looked at RedKite‘s tutorial now again (...excellent as usual) and now I see what I got wrong: I had the HMD as SOI but the cue was apparentyl uncaged already. So it is that the CUE or CURSOR is off the HMD FOV, not the ground object. My misconception was basically crosshairs equals cursor, not understanding that these are two independent things... music_whistling:
  13. Thanks, Ziptie. I get what you are saying. But unfortunately I still don’t see how a point on the ground at which my HMD crosshair is displayed over cannot accurately be designated as SPI „because it is outside of the HMD FOV“?? How on earth can something be under the crosshair but outside of the HMDs FOV at the same time? If it would be outside, how comes I have a crosshair displayed over it?? I must be getting something completely wrong here, hope someone is able to lend me a hand. Thanks.
  14. I struggle to understand what the HMCS „screen“ (video lingo) or FOV actually represents. I mean it isn‘t a sensor itself that looks outside like a TGP but rather a system that just senses the position and orientation of the Helmet relative to the cockpit. I understand that when something is outside of my HUD FOV it is simply not within the area that I can visually identify as my HUD FoV (simply speaking, it is outside of „where I can see symbols“ on the HUD or „where the HUD is unable to display something“). But given that the HMCS symbolgy can be fully seen wherever you look, how do I know I am looking „outside of its FOV“ and so I know when I can make a SPI or not? Thanks.
×
×
  • Create New...