Jump to content

Recommended Posts

Posted

(This subforum looks like the most appropiate to post this...)

 

 

 

First of all, I know this might look like a stupid idea, but looks like it may be able to work.

 

 

My current situation: flying on a laptop, the requirements for 2.5 are too high and is effectively unplayable (not complaining, I know that my laptop is not at all made for gaming, much less for something like DCS), so for the time being I'll be stuck at the last 1.5 version.

 

 

Today I thought that maybe that had changed, so I tried installing the 2.5 beta, only to find out that it is still as impossible to use on this PC as before. So, now I find myself with the 1.5 version installed, the one I fly in, and a 2.5 version with the latest updates but "useless" for me. An idea came out from this:

As the Harrier has been upgraded several times since the merge, updates that I've been missing, and now I have all the files from the current version of the plane, would it be in any way possible to just substitute/copy the correct files from the 2.5 install to the 1.5 install so I can use the newer systems/avionics in the older version? I don't have any real experience or knowledge on the file structure or internal workings of DCS, but after some looking around it appears that luckily it would be somewhat possible...

Also, would it work also for flight model changes or is the FM handled differently?

I hope I worded it correctly to be understood, and that it is a not too stupid question, but desperate times call for desperate measures...

Posted

You CANNOT copy files from One version to Another.

 

The DLLs will have different versions and manifests and automatically fail manifest check on startup and block the module from loading.

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted
You CANNOT copy files from One version to Another.

 

The DLLs will have different versions and manifests and automatically fail manifest check on startup and block the module from loading.

Alright, thanks, at least it was worth a try...

  • Recently Browsing   0 members

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