[OLD BUG REPORTS] Cleaning and Organization of old posts

[imacken]

The Cold Start issue was fixed and works fine in OB as BD said, and I didn't have any C130 issue in the radar TM.

[Neon Knight]

The Cold Start issue was fixed and works fine in OB as BD said, and I didn't have any C130 issue in the radar TM.

Thank you, I'll switch to OB and try "Cold Start" there then.

 

As for radar tutorial, I tried it a couple of times more and everything worked fine, could be I did something terribly wrong on the first attempt.

[=36=Witcher]

Ok, I know that this might sound incredibly weird... but it's been pretty consistent with my setup, so I cannot think about anything else than a bug.

 

A little background first: I have a Thrustmaster Warthog, and running a TARGET script (https://forums.eagle.ru/showthread.php?t=116454). When running scripts, TARGET usually hides all the physical Thrustmaster peripherals involved in the script itself, and replaces them with a Virtual Controller that is used to perform all the nice things TARGET allows to. However, there's an issue in Windows 10 where the Microsoft Store App, which starts at boot, "locks" all the input peripherals, and thus prevents TARGET to disable the individual hardware peripherals before creating the Virtual Controller. As a result, TARGET loads really slowly (about 30 seconds) because it tries to hide the peripherals without success, and you end up with both the Virtual Controller and each single peripherals in DCS. So, for me that I have Joystick, Throttle and two MFDs, that means a total of 5 peripherals in DCS (plus Mouse, Keyboard, Rudder and TrackIR). Anyway, when in DCS->Controls options, I can choose to just not care about the single peripherals, and only map my Virtual Controller. It's a bit annoying to see those extra peripherals that shouldn't be there, but whatever.

 

A few days ago I discovered an easy way to prevent Microsoft Store to start at boot, by simply go in Windows Settings->Privacy->Background Apps and disabling Microsoft Store. After rebooting the PC, Microsoft Store doesn't start anymore, so loading the TARGET script is blazing fast (5 seconds, more and less) and the individual peripherals are hidden. Happy me: no useless peripherals around and quick start. Yay!

 

Except this: don't ask me why, but the Engines START entry will be RED (and won't work with any key combo) if there's only the Virtual Controller. See the attachment.

 

I tried to assign various key combo to Engines START, but they won't work. The same combos assigned to any other controller works fine for those, but as soon as I assign a combo to Engines START, that one is simply ignored.

 

So I started wondering about the cause, and in the end I found that the issue is about which devices DCS sees. Specifically:

 

The Engines START entry is NOT red if:

 

- No Thrustmaster peripherals are connected, OR

- Joystick and/or Throttle are connected AND At least one MFD is connected

 

The Engines START entry IS red if:

 

- At least Joystick or Throttle is connected AND no MFD is connected

 

Which, honestly, is kinda crazy to me. I also tried a simple TARGET script, not the one I use regularly, and the issue is the same. Also phisically disconnecting MFDs and only keeping Joystick and Throttle connected results in this issue to be present.

 

I don't know what to think. I know it sounds crazy, and next thing I'm going to try is to completely wipe all TARGET software and Thrustmaster drivers from the PC and start from scratch. It would be great, at least for my mental health, that someone could prove me wrong showing that Engines START works fine instead and that this is something only on me.

[=36=Witcher]

I finally found the cause!

 

There's a conflict between Engines START and NVG Stow/Unstow in the default keyboard.lua file, as they are both mapped to RShift+Home. I changed NVG Stow/Unstow to LCtrl+Home and now the entry is not marked as an error anymore. I hope this fix can be included in a future release.

Edited May 14, 2020 by Lorthirk

[=36=Witcher]

I also noticed that it was already reported a few months ago here (and also commented by me -- totally forgot!)

[Home Fries]

I forgot too!

 

Any chance this gets fixed (e.g. remapping NVG Stow to RCtl+Home) by the May 20 patch?

[=36=Witcher]

I forgot too!

 

Any chance this gets fixed (e.g. remapping NVG Stow to RCtl+Home) by the May 20 patch?

LCtrl+Home is a better option by the way, as RCtrl+Home is used somewhere in General IIRC

[mrmat01]

Can somone tell me what is wrong with this image ??? :huh:

This is what I got spawned into for the M-2000 No Fly Zone mission. :noexpression:

 

[ATTACH]236042[/ATTACH]

 

Is everything broken about this module? :cry_2::censored:

& yes Im running stable.

[honeycool75]

To add waypoint into the radar scope, I will do this ->

 

Prep -> <waypoint no> -> val

 

However, I've to do this multiple times to get it work and at times it won't.

 

Is anyone else getting this problem?

[myHelljumper]

The waypoint have to be in the FOV of the radar, that means that at the moment you click VAL, the waypoint should be able to show up on the VTB.

That means that if the display is at 40nm and your waypoint is at 60nm it won't work, or if it's behind you.

 

I'm not sure that's how it works IRL but that's how it works in the sim now.

[honeycool75]

The waypoint have to be in the FOV of the radar, that means that at the moment you click VAL, the waypoint should be able to show up on the VTB.

That means that if the display is at 40nm and your waypoint is at 60nm it won't work, or if it's behind you.

 

I'm not sure that's how it works IRL but that's how it works in the sim now.

 

From your explanation, it means the WP has to be within the radar line of sight arc, something I never thought of.

[TaleSpin]

From your explanation, it means the WP has to be within the radar line of sight arc, something I never thought of.

 

Well, your current VTB setting has to be able to show it, since your radar is always looking "to the top" of the display at a given "zoom" (= radar range).

 

It's like looking for a spot on a folded part of a map - you will never be able to see it :)

 

EDIT: Or have a look at it this way: when displaying the WPs, the VTB kind of (!) overlays the radar with an invisible map.

Edited May 19, 2020 by TaleSpin

[imacken]

To add waypoint into the radar scope, I will do this ->

 

Prep -> <waypoint no> -> val

 

However, I've to do this multiple times to get it work and at times it won't.

 

Is anyone else getting this problem?

 

I don't know if it's relevant to your issue, but I have found that in certain missions it doesn't work.

 

Not sure if this can be disabled in ME, but certainly on some stock missions it doesn't work. Maybe some training or instant action. If I come across one again, I'll be more specific.

[frosen]

Yes, that's something I hope they fix. In the meantime just press the mission editor button when you are about to start the mission and move the closest F-15 a couple of hundred meters north.

 

Not the best solution but it works.

[mrmat01]

Yes, that's something I hope they fix. In the meantime just press the mission editor button when you are about to start the mission and move the closest F-15 a couple of hundred meters north.

 

Not the best solution but it works.

 

I tried to edit the mission & fix it but all it did was break it. :eek::confused:

when I hit save The M-2000 just disappeared :huh:

There was no player planes left in the mission at all :crash:

It also has a few other issues with some AI spawning too low & crashing into the mountains.:rolleyes:

[frosen]

I tried to edit the mission & fix it but all it did was break it. :eek::confused:

when I hit save The M-2000 just disappeared :huh:

There was no player planes left in the mission at all :crash:

It also has a few other issues with some AI spawning too low & crashing into the mountains.:rolleyes:

 

You don't need to go into the "real" mission editor but only the one popping up when you're at the briefing page. I don't remember exactly how it says but maybe it's "mission planner" or something like that.

 

Just move the F-15 closest to you, no need to save. Should work!

[mrmat01]

:doh: Why didn't I think of that. Probably because I had tried a bunch of stuff & it was all broken & I was just so frustrated with it all :furious: :badmood:

[Tomsk]

As per the description: some recent patch means that the radios in the Mirage no longer work unless the engine is running. This breaks the campaign that ships with the plane since much of the dialogue in that campaign (and others, e.g. the Red Flag campaign) is given with the engine cold.

 

Tested in Open Beta: 2.5.6.49314

Edited May 22, 2020 by Tomsk

[P3Ci]

So I cannot progress to do 1st mission THE BASICS..

 

As after startup procedure Humveee drives in cl. Lambert and hit his nose and damages it.

 

Any help please?

[Zarco]

Already been reported:

 

https://forums.eagle.ru/showthread.php?t=159851&page=29

 

Only solution is to wait until its patched.

[jojo]

As per the description: some recent patch means that the radios in the Mirage no longer work unless the engine is running. This breaks the campaign that ships with the plane since much of the dialogue in that campaign (and others, e.g. the Red Flag campaign) is given with the engine cold.

 

Tested in Open Beta: 2.5.6.49314

 

This is weird, I can call the ATC with engine OFF to start up.

Are you sure battery and radio are ON ?

[Tomsk]

This is weird, I can call the ATC with engine OFF to start up.

Are you sure battery and radio are ON ?

 

Positive. Yeah so the ATC does work but receiving sounds over the radio (as happens in the campaign) does not work. You can check this by toggling the UHF SIL switch: if only the battery is on you do not hear any static. If the engine or ground power is on, you do hear static.

 

Turning on the ground power does also fix the issue, although as I understand it the ground power is optional in the Mirage (the plane certainly starts without it). It's also very confusing because with just the battery on the radio looks like it should work. The frequency display works, you can change presets or interact with the VHF displays, you can call ATC .. you just can't receive audio.

Edited May 24, 2020 by Tomsk

[krapouk]

The very first post was 12-28-2015

5 years later, still not fixed ^^

Well well, i'm still in love with Razbam :lol:

[frosen]

Yes, had an excellent opportunity to try it in Coup d'Etat M03 when you are to visually ID an unknown aircraft but bummer...it doesn't work. :(

[Xxx]

2.5.6 full release.

 

 

When carrying Cluster bombs and LGB's, there is no EL1 in the PCA. BF6 is shown on PCA 2. BFG s shown on weapons display PPA Test Weapons load-out.

 

 

Can not see LGB (EF1) on PCA when a mixed load is carried.

 

 

Is this a new limitation for realism in the Charlie, or is it a bug?

 

 

Or is it me?

 

 

Cheers.

Edited May 30, 2020 by Accipiter
clarity