Jump to content

Recommended Posts

Posted

The answer was not to transfer anything from 1.2.x to 1.5 because of the switch to Dx11 as well as other things.

(like control assignments that changed, MIG-21 being a prime example)

 

I know, its a pain. But part of the DCS way of life.

[sIGPIC][/sIGPIC]

The keeper of all mathematical knowledge and the oracle of flight modeling.:)
Posted

Actually, I did not have much problems I just needed to delete the general "config.lua" (not 100% sure about the name - cant check now) and started up the openbeta. I got a strange stretched screen, but I could enter the options, reselect the approriate resolution and since then everything worked fine. There was no need to also delete my controller config and it was ported just fine. I dont have the MIG 21 module though. I can 100% confirm that A10C and HUEY did work flawlessly.

Posted

Don't want to encourage bad habits but I saved my 1.2 OB config and pasted it into my 1.5 OB instal and everything worked except for MIG21 throttle assignment. I did this before I saw any posts saying not to and hey it worked for me:)

i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64

[sIGPIC][/sIGPIC]

Posted (edited)

Worked perfectly for me as well but I don't have the MiG-21.

 

EDIT: And isn't the <config>.diff.lua just storing the difference between default assignments and your likings? I would suspect so. Transfer off all .diff.lua between versions should work fine? Or?

Edited by HiJack
Posted

I copied across my diff.lua control files or just imported them via the controller menu (not as quick, but lets you quickly scan down the list, one at a time, to check all is okay).

 

I didn't do this for aircraft that have had relevant changes implemented in 1.5 - just the 'old timers' .

 

FC3 aircraft, A-10C, Ka-50 - that sort of thing.

 

the newer, still in beta, modules I entered manually.

 

No issues thus far.

Rig: Asus TUF GAMING B650-PLUS; Ryzen 7800X3D ; 64GB DDR5 5600; RTX 4080; VPC T50 CM2 HOTAS;

Pimax Crystal Light

I'm learning to fly - but I ain't got wings

With my head in VR - it's the next best thing!

Posted
I copied across my diff.lua control files or just imported them via the controller menu (not as quick, but lets you quickly scan down the list, one at a time, to check all is okay).

 

I didn't do this for aircraft that have had relevant changes implemented in 1.5 - just the 'old timers' .

 

FC3 aircraft, A-10C, Ka-50 - that sort of thing.

 

the newer, still in beta, modules I entered manually.

 

No issues thus far.

 

New control options were added to some if not all FC3 aircraft. In the F-15 at least there are now anti-collision lights and bingo bug controls. Anti-collision I could see being an across the board addition.

  • Recently Browsing   0 members

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