-
Posts
143 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
As of now, both issues are fixed, at least for me! Thanks!
-
Thanks--and sorry, I didn't write what I meant very clearly! Yes, I've been using that workaround, and that does reset the view to normal zoom. The issue is that I can't change what my default view is even after using that workaround (normally bound to RAlt+Num0). That's the thing that only works when I switch to a different seat and back again (if there's one available to switch to).
-
To add to this, I cannot reset my default view angles unless I'm in an aircraft that has multiple seats--I can do it only by swapping from one seat to another and then back to the original seat.
-
Bug still present with 16 November OB patch.
-
I did just have that issue for the first time yesterday--switching from GBU-12 to CBU-97 did seem to cause a problem for me with the GBU-12. Perhaps the issue isn't weapon-specific, but maybe something else?
-
Can strongly recommend anything by Reflected, Baltic Dragon, or Ground Pounder. I don't know what you already have but IMO those three set the standards for DCS campaigns.
-
Ah, that might be the issue then. Got the ILS to work properly on other airfields at hot starts, so that would make sense; I've only been flying out of Nellis with cold starts.
-
FMBluecher started following Mission 11 Map Confusion , Can't Get ILS to work properly at Nellis , GC Alignment loop, doesn't finish and 1 other
-
Don't know if this is user error, early access, or bugs, or what, but ILS at Nellis doesn't seem to be working as it should going from the manual. 1. I enter the ILS frequency into the UFC, which seems to accept it (goes from ILS OFF to ILS 109.10) 2. I select ILSN from the HSI (HUD confirms I'm in ILSN mode to a waypoint on the runway) 3. I enter the course into the HSI I do get the glideslope indicator, but I never get the ILS localizer bars to appear on the HUD or the ADI. Am I doing something wrong? Or is Nellis's ILS broken and I should try a different airfield? AFAIK, Nellis's ILS works for other aircraft, but it's been a hot minute since I tried it. I briefly tried ILST with Nellis's TACAN as well, and that didn't work either.
-
Another relevant factor: do you play mostly multiplayer or single player? A lot of modules are released with very little single player content, but you should be OK for multiplayer.
-
Thanks for checking! I guess I must have fat-fingered the abort option, since I don't use voice attack or anything like that. I didn't think my fingers were close enough, but hey, I was pretty tired when I played it yesterday, so maybe I wasn't self-aware enough to consider that as an option! Thanks again!
-
Trying M12 today, I pulled off of the secondary target in order to get a bit of spacing from it before starting my run when I heard Steep just suddenly abort the attack without my selecting that via the F10 menu. I was then unable to order E-Boy to resume the attack, ask for SEAD, etc. I was a bit to the north of where E-Boy was orbiting, so maybe I wasn't 100% where I was supposed to be, but I figured attack heading didn't matter quite as much since this wasn't a CAS tasking. I was still quite close to the target (less than 9 NM from the Uragans I was targeting)! I can provide a Tacview replay if that would help.
-
nullThe map of the target points for Target Fox has Steep's target point (TGT POINT 2) in the upper-left corner of the map even though the briefing text says "the southeast tower." I am assuming that the target actually IS the southeast tower, but I initially thought it was the northwest one because of the map orientation. If it is the southeast tower, perhaps putting a North arrow on the map might help to orient the player? BTW, overall, amazing work! Took a bit of a break from playing this campaign for a few months and now I'm back at it--absolutely loving it and can't wait to get into Kerman once I'm done!
-
Correction--this issue still doesn't seem fixed for me, either. If I make a brand-new mission, the waypoints work properly. However, if I load a mission that existed previously, incrementing the waypoints via any manner other than the QA menu still doesn't work. Did the update break older missions?
-
Odd advice, but maybe try a second repair? I did one repair post-patch and then another after Ramsay posted. The first one didn't seem to fix it, but the second did. To clarify--the WP increment bind does work but pressing the arrows in the EHSD doesn't? Or do you have to do what I did pre-second repair and pull up the QA menu in order to select any different waypoint at all?