imacken

I really don't understand what is going on here? This is what I see. I installed FC3 then got a bunch of authorisation issues, uninstalled all modules and now this is what I see.

I'm a little confused by this. FC3 is still a thing on my install and there is no way of installing the individual planes.

That's why it's working! The new DCS launcher and Tobii are not compatible. You need to switch it off.

@BIGNEWY is there any word on who is going to be fixing the Tobii Eyetracker issue that has been well discussed since the last patch, i.e. Tobii ET does not work with the new ED Launcher? Is it Tobii or ED who will fix it?

Yes, it would be nice for that to be the way it used to be.

As an aside, are Eagle Dynamics ever going to incorporate Tobii support into DCS so we can stop using GameHub? Most games have it now.

Tobii Eye Tracker 5 not working with this patch unless Launcher is disabled. Lots of unhappy users on Discord.

Yep, I think we’ve established that!

Good to hear!

It’s the time to get to the main menu on the first loading of the day we’re talking about, not mission load times. They’ve always been ok for me.

Yes!

Today, like yesterday, my load times were OK after adding DCS folder to Windows Firewall omit. So, could be good news!

Why would it be a ‘given’? This is a recent development for me. No problem before that. I’ve never omitted anything in a firewall in my life before. Never had a need.

Well, I thought I would give that a go, and today's first launch took 35 seconds! Now, that may be a fluke, so I'll try again tomorrow.

I wonder what is different about the first loading of the day.

Not sure if this has been mentioned by anyone else, but for a long time now, the first loading of DCS in ANY day takes about 3 minutes to get to the menu. Any subsequent load in that same day is fine, i.e. about 20 seconds. Is this a common issue or any suggestions to help with this?

IMO, the best tool for this is JoyPro. An incredibly useful tool for many things in DCS, but particualrly useful for the GUID change that can occur. Once you are set up, if the ID does change, it is literally one click in JoyPro to sort the issue and you are good to go. See here https://github.com/Holdi601/JoystickProfiler As I said, this is just one of the many uses for binding in DCS. Have a look at some of the tutorials. Some are a bit out of date, but still useful.

I get that. However, it would be useful to have a self-accelerator option.

I’m curious, the sanitisation?

Yep, I started the thread on this on the F-4E forum. I took the devs advice and made the edits he suggested. They work well. Well, I say work well, but using the slow option also slows down the rotation speed when holding the switch. It is unusable. So, it means I have to have 8 binds for CRS/HDG instead of 4 which is pretty annoying. I did ask him why it worked OK in the Hornet, but I didn't really understand his reply.

I don't fully understand that, but why can't you use the same logic as the ones that do work well?

Tried your binds, but whenever I make an adjustment to the Heading or Course knob valeues, e.g. change 'value_pressed' to 0.00100, the bind disappears from DCS. Any ideas?

Interesting. As I said above, the exact same device buttons/switch and binds work perfectly in other modules, e.g. Hornet. Quick left or right makes degrees go up by one, and holding the switch makes the dials rotate at a 'normal' rate. I appreciate that the Hornet is a switch, and the F-4E is a knob, but still. In the F-4E, the holding speed is way too slow and pretty much unusable.

Thanks. I was looking at the joystick default, not keyboard. So, there is good news and bad. The good news is that changing to variants and by binding to Course/Heading (Slow) and setting a value of 0.0008, I can get a 1 degree change with a press of the switch. The bad news is that makes holding the switch to move continuously round VERY slow to the extent that it is unusable. I would have to make another bind (to normal or fast) for that, which is not good. The same bind on the same switch/device, works perfectly in other modules, e.g. Hornet, without any fast/slow options.

I just got a reply from one of the Heatblur devs to say that this issue is fixed and will be in the next patch. So, good news!