CFS2 Perma-stickied help / problem / tweaking thread

Hi Mike, think of dll’s as being able to export variables, functions and resources which are imported by cfs.exe. To my understanding the linkage table refers to information being used by the linker from the header .h files during compilation of the dll. Now the problem is without having a cfs specific SDK knowing the various names is impossible to workout with a white hat on.

Take into consideration that much of what’s under the surface of cfs is from fs and doesn’t function properly, like dynamic scenery, atc and logbook just to name a few. There’s even reference to an F-18 in cfs 😂

I’ve been programming some gauges lately and had to customise the fs gauges.h so it creates proper cfs2 gauges

Cheers
Aussie aka Ossie 😝
 
Hi All,

Sarg Willy makes an interesting point regarding adding affinitymask in the cfs2.CFG.

[JOBSCHEDULER]
affinitymask=n


There's a calculator you can use to get the right numbers for your cpu and if it utilizes hyper threading or not. Find the link below.

Gatwick Flight Simulation Group (gfsg.co.uk)

As you mention Sarg you will see temperature increases due to the fact the cpu is working harder which is to be expected and also establishes proof of concept.


Cheers
Aussie
 
Ali Cat

You seem to be able to poke around the CFS2 .dlls any chance you could look at them or the CFS2.exe and find the one that "Enable hardware acceleration" and make it always check-able or make it have "Enable hardware acceleration" always on?
 
That won't help. CFS2 is a DirectX 7 game that doses't play nice with modern cards. Simply put CFS2 doesn't see modern cards as hardware acceleration capable and grays the option out. Editing the CFS2.cfg works but the editing has to be done just about any time you change any other setting too. Annoying AF to do over and over.
 
Allen,


I afraid I do not know of a way to accomplish your request. This investigation I have done into the cfs2 dll's, while I don't regret it, has largely been a bust. From these binary's I can see very little – so many questions left unanswered. In that you sparked my curiosity, I did some searches of the DirectX 7 SDK. There is a sample program that shows how detect if hardware acceleration is supported. It is almost 2 pages long. It could be that there is some 32 bit value in the cfs2 binaries that does what you wish (which I could not find anyway), but I really doubt it is that simple. My somewhat educated guess is that it is buried in code, in binary, which would make it pretty much impossible to decipher.


Aussie,


I know exactly what the “Linkage” export does -- for a gauge file at least. DumpGauges.exe would not be doable if I did not. It is a variable length array of the PGAUGEHDR structure. This structure contains all the data that cfs2 needs to display the gauge. And you went on explaining to me what a dll is? I have written code for 40 years. A request – stay off my threads.


AC but call me Mike
 
Mike,
My apologies but I haven't read your resume. I will most certainly refrain in future from trying to assist you. :untroubled:

Aussie
 
Guys, I have a question, probably a rather stupid one, but anyway..
I bought a new widescreen monitor for my computer. Now, when I run CFS2, and of course also FS9, I get this distorted picture, as the proportions of the new screen are different from the old one.
I didn't find anything in the settings menu of either sim to change the screen proportions.
Is there anything I can change in the settings of the computer itself to get the old picture back? Or maybe in the config files of the sims?
Any help would be highly appreciated.
Thanks.
 
I had the same problem around two years ago, I have a display 3440x1440 but cfs2 can't use the full size without trouble, I suggest making a backup of your "cfs2.CFG" file than hand-edit the cfs2.cfg, after doing that, never ever open the quality settings in cfs2 because cfs2 falls back to "16bit"



open the cfs2.CFG with editor, than serch for Display

my settings are


CFS2.CFG

[DISPLAY]
Device=NVIDIA GeForce RTX 3060
Mode=1920x1200x32
Dither=0
AntiAlias=1


For FSDS2 User: If you have a new big display (>1920x1080) , you will find out that you always get a DirectX error if you use the full screen.
When working with FSDS2, I set the "Windows" display settings to 2560x1440 and everything works fine.

wolfi
 
Wolfi,
Thanks for your suggeston,I tried it but the picture sill looks he same.
However, I now tierd running the sim in windowed mode, and this works okay.
 
When it comes to display settings, here is what I use:

to get hardware texture lighting, and other options to work, I found that I have to had edit them in.

[DISPLAY]
Device=NVIDIA GeForce RTX 3070 Ti
Mode=1920x1080x32
Dither=0
AntiAlias=1
HWTnL=1

CFS2 supports resolutions up to 2048 x 1536.

Other display settings to try in the cfg. file:
Dither=0
Filter=1
TriLinear=1
MipMap=1
AntiAlias=1
HWTnL=1
 
Modifying a dp file

Before all happy new year!

I am slowly daring to use DPed to play around some dp's for some planes, like changing gun sounds or allegiance but when I do that if the plane has some payloads (bombs, rockets) they don't appear on their racks anymore (bombs drop from the inside of the plane and rockets fire through the propeller). I don't change anything else in the dp so I don't understand why it messes things up. Am I doing something wrong while editing the dp?

Sorry if it's a dumb or already answered topic.
 
Ludo said:
Before all happy new year!

I am slowly daring to use DPed to play around some dp's for some planes, like changing gun sounds or allegiance but when I do that if the plane has some payloads (bombs, rockets) they don't appear on their racks anymore (bombs drop from the inside of the plane and rockets fire through the propeller). I don't change anything else in the dp so I don't understand why it messes things up. Am I doing something wrong while editing the dp?

Sorry if it's a dumb or already answered topic.
Click to expand...

Sounds to me like you and DPed aren’t understanding each other much. The changes your making doesn’t require a sophisticated software package just notepad and it’s faster. You just need a little basic knowledge on reading the dp files. You really only need Dpend if your tackling bigger projects but from what I’m seeing it’s better for you to start from the beginning and making simple edits with notepad. One step at a time easy does it.
 
wolfi said:
I had the same problem around two years ago, I have a display 3440x1440 but cfs2 can't use the full size without trouble, I suggest making a backup of your "cfs2.CFG" file than hand-edit the cfs2.cfg, after doing that, never ever open the quality settings in cfs2 because cfs2 falls back to "16bit"



open the cfs2.CFG with editor, than serch for Display

my settings are


CFS2.CFG

[DISPLAY]
Device=NVIDIA GeForce RTX 3060
Mode=1920x1200x32
Dither=0
AntiAlias=1


For FSDS2 User: If you have a new big display (>1920x1080) , you will find out that you always get a DirectX error if you use the full screen.
When working with FSDS2, I set the "Windows" display settings to 2560x1440 and everything works fine.

wolfi
Click to expand...

Once you edit the cog it’s best to make a copy. You can set it to read only to keep changes from happening but if you do that your gonna be starting out in the same airplane and runway you last used before editing the cuff file. You can switch aircraft and runways but when you do it works great but when you exit free flight it goes back to the old airplane and runway not what u last used.
 
Thanks for the replies and for this guide, I will take a look at it :loyal:

I must admit it's kind of intimidating, all those numbers doing differents things and being worried about messing everything up, but yeah, trying things here and there from time to time, to see how it goes. But maybe I should better let this to the pros who know their stuff :playful:
 
You must log in or register to reply here.
Back
Top