Jump to content

Recommended Posts

Posted

Looking through the platcam. 

Looking at aircraft in F2, or ships in F9, etc etc.

You can no longer look around in these views with the mouse when not in VR.

  • 2 months later...
Posted

Yesterday i had this problem, too. Still there after reboot. I'm using the open beta.

And it's not only in the hornet. (Sorry realized i'm in the hornet thread after posting)

 

Panning and zooming by mouse wheel is not possible in F2 view or other external views.

Control of view with keyboard controls is working. (Shift+NumPad /  , ...)

 

The mouse is correctly assigned in axis controls. I didn't change anything there.

 

A friend of mine experienced it about 4 weeks ago, but it went away after an dcs update.

Posted (edited)

I can confirm this, current Open Beta (I use VR). Tested with Mi-24. Before no this issue but few times yesterday I noticed the same (used Mi-24P module). After 10-15 minutes mouse F2 view (panning) stops working, just fixed view. No issue in VC (when I back), mouse cursor works and I click any switch ect. F2 view, agan. Cant panning around the model. I didnt notice it before August’s updates of Open Beta.

 

I see that its a bigger problem than 3 people:

F2 External view - mouse not panning around aircraft.

 

 

Edited by YoYo

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
4 hours ago, Flappie said:

Please ensure this box is NOT ticked:

 

 

 

Thx but I have turn off this from long time:

 

AXjpqyx.jpg

 

I did now test again and noticed it after Change position to Pilot Operator in Mi-24P. I added here my track (more than 5Mb so I use external upload, it will be here 1 month):

https://www.sendspace.com/file/f8jp26 .

On the Track you can notice that from beginning the mouse external view (panning) on F2 works. After when I go to Pilot Operator station and fire the first missile the external panning stops to work. BUT in cockpit it works still without any issue. Looks like a bug, but hard to tell me its a bug in this module only or in the whole DCS.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
33 minutes ago, YoYo said:

On the Track you can notice that from beginning the mouse external view (panning) on F2 works. After when I go to Pilot Operator station and fire the first missile the external panning stops to work. BUT in cockpit it works still without any issue. Looks like a bug, but hard to tell me its a bug in this module only or in the whole DCS.

 

Thanks, I'll try this.

  • Like 1

---

Posted (edited)
1 hour ago, Flappie said:

 

Thanks, I'll try this.

 

Thx, I found this post also:

So maybe Mi-24P module strange bug?

 

Edited by YoYo
  • Thanks 1

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
3 hours ago, Flappie said:

Good, this looks like a proper universal bug. The easier it gets reproduced, the faster devs can fix it.

 

I did more reserch (new created mission in current OB) and for me its an issue with Mi-24P and DCS environment but only if you take pilot operator place plus open and go to Sthurm sight. No any issue with two places modules like: Yak-52, F-14, Mi-8. In Mi-24 if you leave the station the issue with external view F2 and panning mouse on external view start to present. Maybe someone else has some other insights, but I've done a few tests now and it shows up every time, so it's easy to check.

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted

However, when replaying your track, I can reproduce the bug (I take control of the game once your F2 view gets stuck, and cannot move the camera with my mouse either). Strange...

---

Posted (edited)
9 hours ago, Flappie said:

However, when replaying your track, I can reproduce the bug (I take control of the game once your F2 view gets stuck, and cannot move the camera with my mouse either). Strange...

 

Thx Flappie for your attention! You did great support! Btw. I found next post about it.... so maybe in your beta its fixed already?

 

Edited by YoYo

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9-13900 KF, RTX  4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro

Posted
16 minutes ago, YoYo said:

Thx Flappie for your attention! You did great support! Btw. I found next post about it.... so maybe in your beta its fixed already?

 

Yes, I knew about this fix. That's why I tested this on current OB (at least I'm pretty certain I did), and I didn't have the issue. Please let me know if the next OB update fixes the issue for you.

  • Thanks 1

---

  • 1 year later...
Posted
2 hours ago, Flappie said:

Can you please attach a short track showing the issue?

 

I got it to work singleplayer and in another server, so I think it may have been a server-side issue.  Still trying to narrow down where it went wrong. 

492nd Squadron CO (F-15E): JTF-111 -  Discord Link

  • 2 weeks later...
Posted (edited)

I've been seeing this for the past few weeks. I can use the number pad 8, 6, 4, and 2 to move the camera up, right, left, and down, but nothing on the mouse moves the camera.

I have the issue in VR (launching with `--force_steam_VR` for the Varjo Aero fix) and in pancake mode launching with the standard updater shortcut. I also made sure I don't have the TrackIR thingy selected.

noMouseinF2.trk

Edited by Wile E.
Posted

Hi. Thanks for the track. I replayed it, then took control over it and I was able to use the external mouse view.

I think the issue comes from your settings.

Try this:

  1. Rename your "Saved Games/DCS..." folder to "DCS_backup" (do NOT delete it).
  2. Start DCS, and try the external mouse view.

---

Posted

Good! Now you can hunt the file causing this:

Rename the new Saved Games/DCS... folder any way you want (you won't need it anymore), then rename the old one to it's original name. Now browse to Saved Games/DCS.../Config, rename your options.lua to options.lua.bak, and see if that fixes the issue.

---

Posted

Basically all files from the "Saved Games/DCS.../Config" folder.
Maybe some Lua files  from "Saved Games/DCS.../MissionEditor".
And if you find nothing in both, maybe some file from Scripts can be responsible for this.

---

Posted

I found the problem. When I set up an airframe, I bulk remove chunks of keyboard and mouse shortcuts. For example I'll filter the commands to axis only and remove everything, or to MFD and remove everything, before setting up my commands. I somehow managed to remove the mouse settings for external views. This was one of the first things I tried to check, using the in game "Adjust Controls" and checking "General" and "UI". I didn't find it though, because the external view controls are airframe specific (?).

I ended up finding the file "Saved Games/DCS.openbeta/Config/Input/F-16C_50/mouse/Mouse.diff.lua", which only had adjustments to remove "Camera Horizontal View", "Camera Vertical View", and "Camera Zoom View". I deleted the file and that fixed it.

So for anyone who runs into this problem: check your airframe-specific settings (not general for some reason) for "Camera View", and make sure you didn't remove them.

  • Thanks 2
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...