mkel2010

I created a mission on the Normandy 2.0 Map to practice ground attack. I placed a number of ground units at an airport along with several Bf-109s at what the map identifies as parking areas. However, when I fly the mission, the 109's end up at a different airfield roughly 4 miles away and on the opposite end of that airfield from where they were placed. I gave these aircraft nothing to do, no triggers or anything else. I just wanted ground targets. Whenever I go back into the Mission Editor, the 109s are right where i put them, but actually flying the mission they aren't. Admittedly, I'm new at this so I might have done something wrong but this certainly seems like a bug to me.

I am having issues saving some, not all, new snap views. Deleting the snapview.lua file helped somewhat, but I finally had to resort to trial and error editing of the snapview.lua to get one view the way I wanted it. My issue is particular to the P-51D, specifically trying to get a (visible) snap view of the fuselage fuel gauge. (The "stock" snap view for the fuel gauge has the gauge mostly hidden.) Manually setting the camera with the view I wanted, going briefly to the snap view I wanted to save it in and then using RAlt+Num0 resulted in returning to the original view with no changes no matter how many times I tried. Even tried it with a different snap view slot with the same (lack of) results. I didn't have any issues saving other snap views after deleting the original snapview.lua. I was eventually able to configure the view I wanted after about an hour of editing the snapview.lua.

One thing I've noticed is that Beam Eye takes control of the camera so you won't see an image any more with Opentrack's interface. It also means that you'll need to shut down Beam Eye to turn off the camera. Previously with Opentrack by itself stopping tracking also shut off the camera. With Beam Eye, you'll also have the option of different resolutions from your camera, depending on the camera. It's another setting to be aware of if you have issues.

I started playing DCS a short time ago and began with Opentrack and it's built in Neuralnet tracker. I wasn't happy with all the jumping around I got with the video using it. Yesterday I found out about Beam Eye and after watching a couple videos purchased the standalone version. I'm still playing with the configuration but I will say it's much more stable than the Neuralnet tracker.

First of all, I'm not sure if this is the correct sub to put this in or not. I've created several simple missions to practice dead reckoning and pilotage in a P-51D on the Normandy 2.0 Map. When flying the mission, I use Ctrl+K to mark my position on the kneeboard map. This works well - for the first two map pages usually up to the halfway point between the second and third waypoints (page two of the generated maps.) As soon as I get to the third page, the marking stops on the third page but does continue on the fourth and fifth map pages, which are zoomed out views. The mission generates the first three or so zoomed in pages, up to about the fourth waypoint, and the switches to zoomed out map pages of the overall mission routes. The Ctrl+K marking continues to work on these zoomed out pages, which are next to worthless for any kind of navigation. Am I doing something wrong in creating the missions? is there a way to correct this kneeboard map issue.

PM Sent.