NightFlier

Hi guys, I'm one of those eager to fly the F1 and together with other squadrons, members of a joint aviation group, are planning to create a private PvP Campaign recreating the War in Angola. Needless to say, the F1 is one of the main modules we'd like to have in. We should begin to develop that soon and it will take a while to be ready. I know there is not a certain answer about the release date but, according to the actual status of the F1 project, do you think it's reasonable to wait for it?

So, anyone from HB is able to reproduce this issue?

Done, thanks

Same here, I'm copy/pasting my report from the DCS Bugs on Flappie suggestion: I just did a Full Repair and tried (SP via ME, No Mods), the results are: - Mix F-14: Freeze - Mix F-16: No freeze, selected several time the same slot and no issues. - Another Mix F-14: Freeze The freeze usually comes the second time I launch the same mission, few times at the 3rd time. As soon as I click FLY it freezes and after clicking somewhere on the screen it goes like the screenshot attached here. PS: Just to clarify, it does it without exiting the mission but changing or reselecting the same client slot. PSS: Log attached dcs.log

@hornblower793 I just did a Full Repair and tried (SP via ME, No Mods), the results are: - Mix F-14: Freeze - Mix F-16: No freeze, selected several time the same slot and no issues. - Another Mix F-14: Freeze The freeze usually comes the second time I launch the same mission, few times at the 3rd time. As soon as I click FLY it freezes and after clicking somewhere on the screen it goes like the screenshot attached here. PS: Just to clarify, it does it without exiting the mission but changing or reselecting the same client slot.

I'm still having the in game freeze whenever I select another client slot in the same mission (it happens on all missions) or launch the same mission a second time. ++No mods installed++ Here attached the log. dcs.log

Nice to know then, I hope they're going to fix it as it looks such a stupid omission.

Hi guys, I noticed that between the VDI and Standby Attitude indicator there's a lot of difference when looking from a central position (in front of VDI). That's of course the Parallax error of the Standby Attitude but the values look a bit too much considering the instruments are very close to each other. I run some test turning at a different bank angles, pausing the game and looking from both a center position and in front of the standby attitude indicator to eliminate the parallax error. The result was that there is already a basic error of 5-7° (no parallax) + a very marked parallax error giving a huge difference up to 15° at 45° of bank (didn't try at 60°). Having flown with analog standby attitude indicators in real life, positioned further away from the primary display (on the right, like the F14), I think this error is too much as what I got in real life was a simple 1-2° off. Of course, if that's real I'm happy with that, I was just wondering as the difference looks quite weird. Hereunder some screens Thanks

Same, freezing when launching the same mission a second time.

Here I am, another one with this issue...CTD on second load of the same mission.

Hi guys, I've assigned different "Radio item add for group" to different groups. When I join the first slot of a group (all groups are Client units), in the F10 menu I get another group's Radio Item. Selecting another slot of the same group gives the correct Radio Item. PS: I checked a thousand times the assignments and they are all correct (otherwise, selecting another slot would have given a wrong radio item again).

Hi guys, I was testing the F-14 in Siria with the new clouds (Overcast 7 preset) and noticed that although the ambient light was dark (below the clouds) the mirrors showed a bright sunny light. I don't know if it's related to the F-14 module or the environmental rendering so I posted here as it's a weather issue. Here attached a couple of screenshots with mirrors and looking behind, I checked in external view as well and it was dark, so no sunny spots were there. Thanks

Hi guys, I'm experiencing a crash with DCS 2.7 with VPC objects in ME something related to "omni lights". Did you get the same?

Really nice work! Any chance to have an easier way to download all these nice objects? I don't care if it's a huge single pack, lot of space here

Hi @Flappie, actually I haven't got any new crash in mission editor and still using mods (even a couple more now).

Yes, here is a new one but with the same problem: the AI is not engaging, they start to intercept and then they go back soon to the CAP holding again. It's a simple miz with 1 blue vs 2 reds in CAP with Search then engage in zone, 1 EWR. Everyone is within the EWR and the Blue is just out of the zone to be searched for the engagement. If you start and go straight you are in the zone in about 30 sec. I noticed that, given the same light (complete darkness at 2 o'clock local in the PG), changing date gives a different outcome! The mission here attached is on 14th June 2016 at 02:00LT. If you change it to something like 23 June (same time and light stays at an equal level...pitch dark), they engage correctly. TEST Search then engage in zone DARK.miz

They where F-14A and F-4. I reported in the bug forum.

F-14A (HB model) and F-4 enemy, F-16 and F-5 Blue to be engaged (me) Didn't try others

Hi guys, I spent all the day long trying to find out why the same CAPs where not engaging with "Search then engage in zone" in the same base mix I'm using for a cooperative campaign. After hours of testing, I found out it happens during night / darkness times! As soon as I changed to a daylight time they worked perfectly. Regards

UPDATE: after an extensive test, removing units, triggers etc. I found out that it's the Local Time of the mission! During daylight it works, during periods of darkness it doesn't work. Is this a bug or what?

Hi guys, I've been using "Search then engage in zone" for long time for the Enemy AI CAP (red). They have "Search then engage in zone" at the starting point and Race-track orbit between WP 1 e WP 2. I deleted the CAP task so they don't just go and kill everyone in the map The area is full of enemy EWR (red) so Blue contacts are identified (I tried with a Red Awacs as well). The problem is: I enter the Zone for the engage as a Blue and 1 CAP starts to engage me and suddenly turns back (Blue still within EWR, engage zone etc.) and the second CAP doesn't start engaging at all (keep orbiting). They actually start when I enter an SA-6 area, as if the EWR is not working properly and they need the SA-6 to identify me (blue). This situation is on the west side (Lar airport area) in PG Map, I tried on the East side (North of Bandar E-Jask) of the map and it works fine, the CAP has the same settings, same plane and loadout, except for the area to be coverd for the engagement. Any help guys?

That's a very good proposal, I hope it's going to be considered by the HB team.

It's too static, I mean, it doesn't change with RPM and make you feel like you are on the ground at the parking stand even if you are flying in MIL Power at 500 Kts. Please fix it or remove it If I can delete it, let me know how to do it because it's really annoying.

Hi @Flappie I've done all the cleaning you suggested but today I got another crash in ME, this time selecting a boat in the group unit. (I want to point out that the crash happens randomly and not so frequently) Here is the log. dcs.log.old

Like others have reported, the engine intake whine noise keeps the same volume/pitch regardless of the RPMs and Canopy position. The effect is giving a reduction in immersion as it sounds like you are standstill at the parking spot...Please fix it or remove it