honeycool75
Members-
Posts
89 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by honeycool75
-
I turned on the NVG for the first time and it appears too bright and blurry even with JVN on and all lights off. I compared to the Youtube preview from Razbam and it looks so nice. See attached screenshots comparison. I can't find any switches to increase or decrease the gain. Can someone tell me what I'm getting is indeed normal?
-
Barometric Altitude showing negative in Syria Map
honeycool75 replied to honeycool75's topic in M-2000
I always thought INS alignment does that... Ok, I will try this. Tx. -
It's unfortunate we can't have a soft lock box on the target without switching to either the gun or missile after the latest M2000C update.
-
In the Syria map only, I'm getting -ve altitude after proper INS alignment. I've double-checked in other maps, this problem doesn't exists anywhere else. Can someone help to cconfirm whether this is already a known issue?
-
[NOT A BUG]EAC Switch Always Off Position
honeycool75 replied to honeycool75's topic in Bugs and Problems
Here's my trk file showing the EAC switch problem. I was in the Instant Action -> Syria -> Cold Start A10C-II-EAC-Problem.trk -
EAC behind the left throttle can't be switch to ON position, always goes back to OFF position. Steps to replicate: 1. Complete INS alignment. 2. Select Nav from MFCD 3. Click EGI switch 4. Click EAC switch EAC works fine in the original A-10C.
-
Thanks for confirming the problem :thumbup:
-
Thanks for the link.
-
I noticed using the TDC to lock target doesn't box that target in the Hud after the recent updates. To see the target lock in the Hud will need to select a weapon. Was this implementation intended?
-
I experienced two issues when performing AAR: 1. If the Mirage was without a drop tank, the tanker will never say "transfer complete, disconnect" when finished refueling. 2. When flying formation, tanker was at 250 kias but the Mirage would be at approx 261kias. Using the same AAR mission, Hornet's speed would be at 252kias. It appears the Mirage has a larger speed gap.
-
[REPORTED]Sometimes no sound when starting DCS 2.5.6
honeycool75 replied to Andy t's topic in Sound Bugs
After updated to DCS 2.5.6.55363 Open Beta, I've to use the autoexec.cfg -> sound.channel_mask = 3 else there will be zero audio in my headset. My usual audio settings are (without having to use the above file): Main audio out = my PC speakers Headphones => my headset -
Does anyone know if the Mirage has altitude warning sound like e.g. the F-18? I crashed at times when flying low while turning my head to spot the enemy planes from the six or avoiding missiles.
-
Finally found out the root cause. The ATC menu - Request Startup, if triggered will cause the cat deck crew not to function. Thought to share it here if anyone's stuck with the same issue. So, stay away from that ATC command, at least for this SC SP mission.
-
Yeah, I tried that too before posting here. Didn't work.
-
I just fired up the stock SC PG cold start mission after a month. Strange that the yellow shirt director stand there no longer giving instructions to line up with cat for take off. It used to work without problems in the past. Could this be a bug due to several updates after the initial SC early access release?
-
Alright, I found out about the problem. I had to set for bomb release count to be at least 01. It works now even for GBU buddy lasing.
-
I'm trying out CCRP for the first time today. I did the following: 1. Select bomb 2. Radar on and Alt on 3. Select TAS and RS 4. Set fuse to instant 5. Designate the target 6. Master arm on When the horizontal line move upward and passes thru, press and hold trigger. However, the bomb won't release. Did I miss a step? P/S: I've no problem with CCIP bomb release.
-
Is there a user created mission downloadable from the web to test out Mirage GBU whereby the target is lased by AI? Thanks.
-
Since the Mirage is without a targeting pod, how do we go about buddy lasing? I watch a few videos where to enable CCRP, the pilot will have to manually designate the target while your buddy is supposedly lasing. This not like the Harrier where there's a function to scan for lased targets. My point is, how do we coordinate the effort, i.e. manual designate the correct target that is currently lased? There's a lot going on during a mission. Hope to get some pointers here.
-
With regards to the NVG, I'm aware 2 ways of loading the case into the Mirage, ground crew or mission editor. On a few occasions during MP missions, I requested the ground crew to load the case, the crew complied and confirmed. However, the case was missing. Has anyone experienced this problem?
-
About the vaicom editor keyword training mode and after the recent update v2.5.20, simple keywords such as vector and tanker which used to be easily recognized, are no longer working. During the keyword training session, the ms voice recognition will request to "spell it" if it can't understand my pronunciation. So, I spelled it and the "Finish" button gets to light up. If I click on that button, it will export to a file. Questions: 1. The keyword "vector" is not found in the editor list, was it ever been there before? 2. Does the keyword training store the outcome, i.e. the user's individual pronunciation somewhere so that it could recognize from now on after the training session? It appears the experience are kinda of erratic for me. 3. Clicking the "Finish" button, exporting to a file, what will I do with that file?
-
I noticed the Mirage easily gets stuck on the ground or grass, e.g. if I accidentally roll off from the asphalt into the sand. 99% of the time afterburner won't help to get the plane moving. Is this realistic?
-
I am on latest open beta. Is the Mirage radar that weak?
-
I was practising Mirage BVR using the stock SP Caucasus destroy F16s AI mission. Attempted 4 times, PID/TWS won't see any blip even the bandits were 40nm dead ahead, moving the radar antenna up down doesn't seem to have any effect. Later, I tried BVR by creating a fast mission, TWS worked. Any comment?
-
Please refer to the attachment, I have a clean startup without any warning lights. While the plane is on the ground, if I'd mess around by intentionally changing the FBW Gain to something incorrect and change it back to normal, several warning lights will appear, MAN/DOM/BECS. These warning lights will stay on forever even though I reverted the changes back to original. Is this expected by design or a bug?
