derekb1948

THANKS Andrey and your team! I have just "flown" the Spitfire with the SimShaker input, after the auto-update to version 1.0.0.20 and it is magnificent - a fine gift for Christmas. Have a wonderful Christmas and a peaceful holiday, and thanks for making sim-flying so much more enjoyable! Regards, Derek B.

I also use a triple-monitor setup and spend a lot of time resetting fields of view in the various lua-files after updates, with a 150-degree FOV being my preferred setting. I can then use the zoom functions to adjust the view to suit the situation. Some while back a feature was added to the "Special" options for the Mi8, where one can drag a slider to increase the FOV up to 150-degrees, thus making it unnecessary to change any of the Mi8 files files after updates. Could this feature not be added for all the aircraft? It would certainly solve the issue.

Hi BigNewy, I followed your suggestion - removed recent mods and ran a repair - and all is well, I can access weapon-loadout with the '109 again. Many thanks for your kind help. Derek B.

Hi BigNewy, thanks for the help! I shall try removing all mods and run a repair and report back, Derek B.

Thanks, BigNewy, I have followed your instructions, so hopefully the relevant files are attached. Logs.zip

Since the last update (1.5.4.5.4080.100) I am unable to adjust the '109s loading in the mission editor. this applies to both the setting-up of a new mission and any attempt to adjust the loads in an existing mission. In either case the program stops working. Has anyone else got the same problem?

Thanks again, Art-J, its good to know some-one's got my back on this one.

Thanks, Art-J, I suppose I needed that wake-up call. Thanks to your clear and detailed explanation I shall give it a go.

Thanks, NeilWillis, I had a look but find it a bit complex for my limited computer-knowledge (I'm in my late 60's, and try to avoid getting in "over my head", if possible). I do normally manage when it's a matter of placing files manually.

This looks like a very useful add-on. Where would one put the new files? I have tried to find a location, but with no success.

Hello Andrey, I have just collected my jetseat from my local Post Office, and wish to thank you again for your really great service and kind help. It arrived in perfect condition (not guaranteed here in Africa), and the tracking system was excellent, with regular e-mails up until this morning when it informed me that the package was at my local Post Office and cleared for collection. Now I look forward to getting it set up and running! The whole process took about 6 weeks which is very good for any foreign order to this country. Thanks, Andrey! Regards, Derek B.

Thanks, Apache600, very useful set of checklists

I think that this can be adjusted in the TrackIR "Motion Adjustment" settings (it's one of the X,Y or Z settings). I had this problem a while back, and managed to get it working this way.

"Price-rises", in the context of this type of product, are really a reflection of monetary inflation, a sad reality for many countries in this day and age. I doubt that the good folk who are producing these stunning products, that give us so much pleasure, would survive as breadwinners for themselves and their families without some sort of price-adjustment now and then to try and keep up. What we pay for their services is, after all, what constitutes their salaries, at the end of the day.

Brilliant! Knowing that it's still in the pipeline has made my day!

With the latest update (Friday, 13th Nov.) the DK2 functions up to the loading of a mission but DCS World stops working every time before mission loading is complete (as it did on the first release of the Open Beta). Has anyone else experienced this problem? I have just seen that this has been reported as a bug.

No, I just added the updates, as described, and the full Oculus DK2 function was back. (I am running Windows 10).

I also lost the Oculus function completely, but got it back by updating the Oculus runtime to version 0.8.0.0 and also updating the Nvidia drivers to version 358.87, as specified on the Oculus website.

I have only loaded a few aircraft onto the DCS 1.5 Open Beta, and, with the latest update, have the cockpit option boxes. The dropdown menus don't seem to be working, though, as they only offer "default" or are blank. Do I have to activate this feature somehow?

I have been experiencing similar problems relating to views, view-resets and cockpit camera adjustments since the latest patch - mostly when using the DK2 but also (with the '109K-4) on normal monitors (with or without TrackIR5 ). I have been experimenting with the FW190D-9, the Me109K-4 and the Su25T in the Open-Beta DCS1.5. The main issues have been with "Num5" (centre view default key) sporadically working, inability to assign the "Num5"-function to other keys (reassigned keys confirmed as mapped but not working) and non-functioning of the cockpit-camera keys (default and reassigned) for left/right/up/down functioning. I am no computer-wizard (dating, as I do, from the first half of the last century!) so these issues could be entirely due to my own bungling and not be "bug"-related. At the present time I seem to have the functions working most of the time in the FW190D-9 and Su25T but seem to have lost the functioning of both the default and re-assigned view-related "Numpad" keys as regards the Me109K-4, except for the (default, centring) "Numpad5" key in all the various configurations. I don't have any modifications set in the DCS1.5 Open Beta, and all the current view-related issues were not present prior to the latest patch. Does anyone have any suggestions regarding sorting this out?

I stand corrected! Thanks for the clarification. I have always set max nose-down trim on the '109, and had not realized the way it was actually operating.

The '109K tailplane incidence can be trimmed using a rotary axis - I am using the "trim1" axis on the G940 joystick.

Yes, I can confirm the issues with the kneeboard and map in 1.5 when using the DK2, so it's surely a universal problem with the Open Beta that would be addressed before final release.

Hello rcjonessnp175, thanks for the assistance and advice. Before I could try your method, a friend who was aware of my problem called to suggest that I "untick" the "full screen" box in DCS and try again. It worked! I now have my cockpit control back.

I am having a strange problem with the Oculus DK2. It was working without problem until I updated a number of components of my computer (motherboard, graphic card, RAM and processor). After reinstalling all my modules they work with the DK2 excepting for the ability to operate functions in the "clickable" cockpits using the mouse. It seems as if the "contact points" for the various buttons, levers, etc., have gone way out of synchronization with their visual positions in the cockpits. The cursor is picking up control points way up in the "sky" above the left wing. I can't locate any information on calibrating the mouse cursor with the contact positions in the cockpit when using the DK2. Has anyone else had this problem, or is there a thread that addresses it? The cockpits remain "clickable" in normal 2D mode, when not using the DK2.