Blackbird Sims / Milviz Forum Archive

Hello,

I could install the new Talon, but it is not possible to fly it. No reactions on any controllers, no sound, no switch is clickable. I checked everything from your support requeat page, everything is there as it should be, only CC+2015 could not ben installed, because of a newer version in my Windows 10. What could be the reason? I installed on the same day the porter, this plane is working fine as well as my 727.

Best regards

Peter

Please enable Content Error logging in your P3D General settings and then post the log after loading the 38A.

Also, is your P3D Academic or Pro?

Hi,

it is the pof Version. Where can I find the error log?

Best regards

peter

Hi,

I hope this is what you asked for.

[error.0]
error=Unable to find model for veh_lkpr_lavatory1

[error.1]
error=Unable to find model for LFMN_SVET2

[error.2]
error=Unable to find model for LFMN_RAIN

[error.3]
error=Found Duplicate Key Name
File:E:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Alabeo C172RG_CutlassII\aircraft.cfg
Section:propeller
Key:minimum_reverse_beta

[error.4]
error=Found Duplicate Key Name
File:E:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Carenado PA42_Cheyenne_III\panel\panel.cfg
Section:Window05
Key:gauge00

[error.5]
error=Found Duplicate Key Name
File:E:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Carenado PA42_Cheyenne_III_LITE\panel\panel.cfg
Section:Window05
Key:gauge00

[error.6]
error=Found Duplicate Key Name
File:E:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Douglas_C-47_Beta_V3.14\panel\panel.cfg
Section:Window05
Key:window_pos

[error.7]
error=Found Duplicate Key Name
File:E:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Alabeo C172RG_CutlassII\aircraft.cfg
Section:propeller
Key:minimum_reverse_beta

[error.8]
error=Found Duplicate Key Name
File:E:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Alabeo C172RG_CutlassII\aircraft.cfg
Section:propeller
Key:minimum_reverse_beta

[error.9]
error=Failed to locate the following script: MVT38Cformlight.lua. Verify all content pathing is correctly configured.

[error.10]
error=Taxiway path with 0 width


[error.11]
error=Taxiway path with 0 width

[error.12]
error=Taxiway path with 0 width

[error.13]
error=Taxiway path with 0 width

[error.14]
error=Taxiway path with 0 width

[error.15]
error=Taxiway path with 0 width

[error.16]
error=Taxiway path with 0 width

[error.17]
error=Taxiway path with 0 width

[error.18]
error=Taxiway path with 0 width

[error.19]
error=Taxiway path with 0 width

[error.20]
error=Taxiway path with 0 width

[error.21]
error=Taxiway path with 0 width

[error.22]
error=Taxiway path with 0 width

[error.23]
error=Taxiway path with 0 width

[error.24]
error=Taxiway path with 0 width

[error.25]
error=Taxiway path with 0 width

[error.26]
error=Taxiway path with 0 width

[error.27]
error=Taxiway path with 0 width

[error.28]
error=Taxiway path with 0 width

[error.29]
error=Taxiway path with 0 width

[error.30]
error=Taxiway path with 0 width

[error.31]
error=Taxiway path with 0 width

[error.32]
error=Taxiway path with 0 width

[error.33]
error=Taxiway path with 0 width


[error.34]
error=Taxiway path with 0 width

[error.35]
error=Taxiway path with 0 width

[error.36]
error=Taxiway path with 0 width

[error.37]
error=Taxiway path with 0 width

[error.38]
error=Taxiway path with 0 width

[error.39]
error=Taxiway path with 0 width

[error.40]
error=Taxiway path with 0 width

[error.41]
error=Taxiway path with 0 width

[error.42]
error=Taxiway path with 0 width

[error.43]
error=Taxiway path with 0 width

[error.44]
error=Taxiway path with 0 width

[error.45]
error=Taxiway path with 0 width

[error.46]
error=Taxiway path with 0 width

[error.47]
error=Taxiway path with 0 width

[error.48]
error=Taxiway path with 0 width

[error.49]
error=Taxiway path with 0 width

[error.50]
error=Taxiway path with 0 width

[error.51]
error=Taxiway path with 0 width

[error.52]
error=Taxiway path with 0 width

[error.53]
error=Taxiway path with 0 width

[error.54]
error=Taxiway path with 0 width

[error.56]
error=Taxiway path with 0 width

[error.57]
error=Taxiway path with 0 width

[error.58]
error=Taxiway path with 0 width

[error.59]
error=Taxiway path with 0 width

[error.60]
error=Taxiway path with 0 width

[error.61]
error=Taxiway path with 0 width

[error.62]
error=Taxiway path with 0 width

[error.63]
error=Taxiway path with 0 width

[error.65]
error=Taxiway path with 0 width

[error.66]
error=Taxiway path with 0 width

[error.67]
error=Taxiway path with 0 width

[error.68]
error=Taxiway path with 0 width

[error.69]
error=Taxiway path with 0 width

[error.70]
error=Taxiway path with 0 width

[error.71]
error=Taxiway path with 0 width

[error.72]
error=Taxiway path with 0 width

[error.73]
error=Taxiway path with 0 width

[error.74]
error=Taxiway path with 0 width

[error.75]
error=Taxiway path with 0 width

[error.76]
error=Taxiway path with 0 width

[error.77]
error=Taxiway path with 0 width

[error.78]
error=Taxiway path with 0 width

[error.79]
error=Taxiway path with 0 width

[error.80]
error=Taxiway path with 0 width

[error.81]
error=Texture MILVIZC310_LANDINGLIGHT_FRESNEL..DDS failed to load (FE_REQUEST_STATUS==13)

[error.82]
error=Texture MILVIZC310_LANDINGLIGHT_FRESNEL..DDS failed to load (FE_REQUEST_STATUS==13)

[error.83]
error=Payload station indexes should be between 1 - 14



Best regards



Peter

Unfortunately we have to be stricter in enforcing use of our non commercial licenses in P3D Academic. I can only suggest that you get the academic version of P3D and install just the client. You can still keep your pro license if you have legal concerns.

Hi,

wth the latest update it should be working now with the prof version. But I have still the same problem.

Best regards

Peter

You using Pro or Pro Plus?

hi Jonathan,

i am using the pro Version.

Actually I am thinking about do unistall MVAMS and do a fresh new installation: Before updating to your new Version i deleted the former Version, but it was still to be seen in MVAMS.
Peter

Hi Jonathan,

ailerons and clicks with the mouse in the cockpit is working now. But throttles are only working with keys, not with Joysticks which are assigned inside the simulator, not through fsuipc. Any solution?

Best regards

Peter

There are some posts on the topic. Will check

Now I have noticed also the same problem with the otter. I am not willing to spend any more time to get your planes to work in prepar3d v4 prof, this is the end of our relation.

Best regards

Peter

Since you are using FSUIPC, you need to send your throttle inputs to FS as a normal axis, using the AXIS_THROTTLE_SETx events.