Jump to content

After installation of 1.11 - check this .....


Finn

Recommended Posts

After installation of the 1.11 update, please check the following:

For non accel users, You should manually remove the slashes before:

//only for Non Accel users

//gauge11=Viper!AS_AB, 0,0,1,1

So it reads:

//only for Non Accel users

gauge11=Viper!AS_AB, 0,0,1,1

Both in the:

\FSX mainfolder\simobjects\aeroplane\Aerosoft F-16A 9\panel\

and

\FSX mainfolder\simobjects\aeroplane\Aerosoft F-16AM Display\panel\

folders.

For Acceleration users the slashes should remain !

Sorry if that not was clear.

The reason is that the auto installer checks what version is installed and put´s in the correct panel.cfg version.

The small 1.11 update though doesn´t do that.

Finn

Link to comment
Share on other sites

After installation of the 1.11 update, please check the following:

For non accel users, You should manually remove the slashes before:

//only for Non Accel users

//gauge11=Viper!AS_AB, 0,0,1,1

So it reads:

//only for Non Accel users

gauge11=Viper!AS_AB, 0,0,1,1

Both in the:

\FSX mainfolder\simobjects\aeroplane\Aerosoft F-16A 9\panel\

and

\FSX mainfolder\simobjects\aeroplane\Aerosoft F-16AM Display\panel\

folders.

For Acceleration users the slashes should remain !

Sorry if that not was clear.

The reason is that the auto installer checks what version is installed and put´s in the correct panel.cfg version.

The small 1.11 update though doesn´t do that.

Finn

Link to comment
Share on other sites

Please note that after update 1.20, the afterburner (gauge 12 in the Panel.cfg in this folder: \FSX mainfolder\simobjects\Airplanes\Aerosoft F-16A 9\panel\) is still marked out. So I recommend to remove the // of that rule so it reads again, correctly:

gauge12=Viper!AS_AB, 0,0,1,1

In F-16AM Display this does not occurs.

Oh, I do not work for Aerosoft, I only assume this is a small mistake in the update to version 1.20 ;-)!

Link to comment
Share on other sites

Yes for non Acceleration users the // should be removed as described above.

Those using the Shockwave Rdux lights also will have to "re-enable" them after installing 1.20.

Sorry for any inconvenience, but progress has it´s backsides ;)

Merry Chrismas for all by the way :)

Finn

Link to comment
Share on other sites

ok, this may sound weard but i removed the complete f-16 package from my pc. I have reïnstalled the f-16 version 1.00 and then installed the update version 1.10, and this is where i stay, version 1.10 works fine for me. every update after that was a step back on my pc <_< . I'm nothing with a 1.20 version if after the update you can't lift your aircraft from the ground!!!

Still want to say that you developers did a real hit with this product, it's wonderfull. Flying the f-16 is everytime again a joy... "heaven on earth"!!! or like history say's about this bird "the fury of the fighter" ;)

regards

nick

Link to comment
Share on other sites

Those using the Shockwave Rdux lights also will have to "re-enable" them after installing 1.20.

Sorry for any inconvenience, but progress has it´s backsides ;)

Mr. Finn,

Can you make the next installer automatically configure the Aircraft.cfg for the LIGHT changes, for REDUX or Default lights, based on user input? :unsure:

Thanks! ;)

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use