Another lighting issue... sorry (and Radios)
-
- Site Admin
- Posts: 1728
- Joined: Mon Sep 08, 2008 4:18 pm
Re: Another lighting issue... sorry (and Radios)
First off, make SURE that you are running the sim as an admin.
Next, make sure that your AV is not scanning the sim directory... and that it wasn't on when downloading and installing.
Next, make sure that your AV is not scanning the sim directory... and that it wasn't on when downloading and installing.
-
- Posts: 3446
- Joined: Sat Mar 13, 2010 7:38 pm
Re: Another lighting issue... sorry (and Radios)
Also please go to start menu->Search->Event Viewer and then go to Windows Logs\Application, right after running the T-38. Look for errors involving the Milviz Lighting service and post the report here.
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
Yes, I did receive several error messages there with lightning and several other effects. Do you think that could be from V4.2? I am definitely always running it as admin. AV was totally off when installed, but I leave it on now. Could that be causing it?JonathanBleeker wrote: ↑Sat Apr 07, 2018 6:51 pmAlso please go to start menu->Search->Event Viewer and then go to Windows Logs\Application, right after running the T-38. Look for errors involving the Milviz Lighting service and post the report here.
- doodlebug
- Posts: 1642
- Joined: Sun Feb 19, 2017 2:49 pm
- Location: LYX>YUL
Re: Another lighting issue... sorry (and Radios)
Is your AV prevented from scanning your installation / sim folders?
-
- Posts: 3446
- Joined: Sat Mar 13, 2010 7:38 pm
Re: Another lighting issue... sorry (and Radios)
Please post the error reports regarding the lighting.
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
There are more error messages then I can type in an hour there hahaha.JonathanBleeker wrote: ↑Sun Apr 08, 2018 7:46 amPlease post the error reports regarding the lighting.
-
- Site Admin
- Posts: 1728
- Joined: Mon Sep 08, 2008 4:18 pm
Re: Another lighting issue... sorry (and Radios)
Copy paste.
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
[error.0]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.1]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.2]
error=Failed to load visual effect "MilVizC310_TaxlBloom_01"
[error.3]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.4]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.5]
error=Failed to load visual effect "MilVizC310_TaxlBloom_01"
[error.6]
error=Texture WING01.DDS failed to load (FE_REQUEST_STATUS==13)
[error.7]
error=Texture WING01_NORMAL.DDS failed to load (FE_REQUEST_STATUS==13)
[error.8]
error=Texture T38C_3_T.DDS failed to load (FE_REQUEST_STATUS==13)
[error.9]
error=Texture T38C_3_T_BUMP.DDS failed to load (FE_REQUEST_STATUS==13)
[error.10]
error=Texture T38C_3_T_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)
[error.11]
error=Texture MILVIZC310_LANDINGLIGHT_FRESNEL..DDS failed to load (FE_REQUEST_STATUS==13)
[error.12]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.13]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.14]
error=Failed to load visual effect "MilVizC310_TaxlBloom_01"
[error.15]
error=Failed to load visual effect "MilVizC310_TaxlBloom_01"
[error.16]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.17]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.18]
error=Failed to load visual effect "MilVizC310_TaxlBloom_01"
[error.19]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 (>L:ffb128e17,enum)
1 (>L:Init6,bool)
}
"
[error.20]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.21]
error=Gauge/Script Error
Type: Visibility Script
Name: T38A_ADV TB7
Error: Invalid script (no command is more than 4 characters): "a90d74 ==
"
[error.22]
error=Failed to load visual effect "MilVizC310_TaxlBloom_01"
[error.23]
error=Gauge file not found: fa-18!hud_2d
[error.24]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\AoA_Gauge_Bgnd.bmp
[error.25]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\Slow_ON.bmp
[error.26]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\Okay_ON.bmp
[error.27]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\Fast_ON.bmp
[error.28]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Expected a E or . after digits: "4== if{
(C:fs9gps:FlightPlanIsLoadedApproach) d (>C:fs9gps:blinkingFieldEnabled1) (>C:fs9gps:blinkingFieldEnabled2)
}
(C:fs9gps:enteringInput) 10 == if{ (C:fs9gps:IcaoSearchCurrentIcao
[error.29]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "True" in: True
[error.30]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Empty parentheses or closing parenthese missing: "(A:GPS IS APPROACH ACTIVE), bool) {if}
((A:GPS APPROACH WP TYPE), enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
{:7}hold
{:8} ((A:GPS TARGET DISTA
[error.31]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "bool" in: bool) {if}
((A:GPS APPROACH WP TYPE), enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
{:7}hold
[error.32]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Empty parentheses or closing parenthese missing: "(A:GPS APPROACH WP TYPE), enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
{:7}hold
{:8} ((A:GPS TARGET DISTANCE, nmiles)) !0.1f!\{dpl=nm}
{:9} ((A:
[error.33]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "enum" in: enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
{:7}hold
{:8} ((A:GPS TARGET DISTANCE, nmiles)) !0.1f!\
[error.34]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup)
(C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{
3 (>C:fs9gps:numberOfBlinkingFields)
[error.35]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup) quit }
(C:fs9gps:popupMenu) 0 != if{ 0 (>C:fs9gps:popupMenu) (C:fs9gps:blinkingFieldSaved) (>C:fs9gps:blinkingField) 0 (>C:fs9gps:blinkingFieldSaved) 70 (>C
[error.36]
error=Macro redefinition 'TerrainButton'
[error.37]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (no command is more than 4 characters): "@NRSTButton"
[error.38]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup)
(C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{
3 (>C:fs9gps:numberOfBlinkingFields)
[error.39]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup) quit }
(C:fs9gps:popupMenu) 0 != if{ 0 (>C:fs9gps:popupMenu) (C:fs9gps:blinkingFieldSaved) (>C:fs9gps:blinkingField) 0 (>C:fs9gps:blinkingFieldSaved) 70 (>C
[error.40]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup)
(C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{
3 (>C:fs9gps:numberOfBlinkingFields)
[error.41]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Expected a E or . after digits: "4== if{
(C:fs9gps:FlightPlanIsLoadedApproach) d (>C:fs9gps:blinkingFieldEnabled1) (>C:fs9gps:blinkingFieldEnabled2)
}
(C:fs9gps:enteringInput) 10 == if{ (C:fs9gps:IcaoSearchCurrentIcao) (>C:fs9gps:
[error.42]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "True" in: True
[error.43]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Empty parentheses or closing parenthese missing: "(A:GPS IS APPROACH ACTIVE), bool) {if}
((A:GPS APPROACH WP TYPE), enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
[error.44]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "bool" in: bool) {if}
((A:GPS APPROACH WP TYPE), enum) {case}
{:2}proc. turn
{:3}proc. turn
[error.45]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Empty parentheses or closing parenthese missing: "(A:GPS APPROACH WP TYPE), enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
{:7}hold
{:8} ((A:GPS TARGET DIS
[error.46]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "enum" in: enum) {case}
{:2}proc. turn
{:3}proc. turn
{:6}hold
{:7}hold
[error.47]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Empty parentheses or closing parenthese missing: "(A:NAV2 HAS NAV, bool)(if{ (A:NAV2 CDI,number) } els{ 0 }"
[error.48]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE
[error.49]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE
[error.50]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Empty parentheses or closing parenthese missing: "(if{ (A:HSI CDI needle,number) } els{ 0 }"
[error.51]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE
[error.52]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ")" in: )
[error.53]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE
[error.54]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ")" in: )
[error.55]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE
[error.56]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE
[error.57]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ".7" in: .7
[error.58]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ".45" in: .45
[error.59]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ".45" in: .45
[error.60]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup)
(C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{
3 (>C:fs9gps:numberOfBlinkingFields)
0 (>C:fs9gps:blinking
[error.61]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (no command is more than 4 characters): "@FPLButton
quit
}
}
(C:fs9gps:currentGroup) 4 == if{
(C:fs9gps:blinkingField) 1 == if{
0 (>C:fs9gps:currentGroup)
1 (>C:fs9gps:currentPageNAV)
(C:
[error.62]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup) quit }
(C:fs9gps:popupMenu) 0 != if{ 0 (>C:fs9gps:popupMenu) (C:fs9gps:blinkingFieldSaved) (>C:fs9gps:blinkingField) 0 (>C:fs9gps:blinkingFieldSaved) 70
[error.63]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_NEAREST_BUTTON"
[error.64]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_OBS_BUTTON"
[error.65]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_MSG_BUTTON"
[error.66]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_TERRAIN_BUTTON"
[error.67]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup)
(C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{
3 (>C:fs9gps:numberOfBlinkingFields)
0 (>C:fs9gps:blinking
[error.68]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_CLEAR_ALL_BUTTON"
[error.69]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup) quit }
(C:fs9gps:popupMenu) 0 != if{ 0 (>C:fs9gps:popupMenu) (C:fs9gps:blinkingFieldSaved) (>C:fs9gps:blinkingField) 0 (>C:fs9gps:blinkingFieldSaved) 70
[error.70]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_CLEAR_BUTTON_DOWN"
[error.71]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_CLEAR_BUTTON_UP"
[error.72]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:currentGroup)
(C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{
3 (>C:fs9gps:numberOfBlinkingFields)
0 (>C:fs9gps:blinking
[error.73]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_MSG_BUTTON_DOWN"
[error.74]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Unknown Event ID: "G1000_MFD_MSG_BUTTON_UP"
[error.75]
error=Gauge/Script Error
Type: Gauge
Name: FBS_KAP140
Error: Invalid variable (missing : - did you forget a macro?): HDGDisp1
[error.76]
error=Gauge/Script Error
Type: Gauge
Name: FBS_KAP140
Error: Missing gauge image file: T38_Base\KAP140_bg_On.bmp
[error.77]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\AoA_Gauge_Bgnd.bmp
[error.78]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\Slow_ON.bmp
[error.79]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\Okay_ON.bmp
[error.80]
error=Gauge/Script Error
Type: Gauge
Name: T38_Logic
Error: Missing gauge image file: T38\Fast_ON.bmp
[error.81]
error=Gauge/Script Error
Type: Gauge
Name: EFFECTS
Error: Invalid script (no command is more than 4 characters): "else{
(A:GENERAL ENG MIXTURE LEVER POSITION:1,percent) 99 < if{
16383 (>K:MIXTURE1_SET)
}
(A:GENERAL ENG MIXTURE LEVER POSITION:2,percent) 99 < if{
16383 (>K:MIXTURE2_SET)
}
}
(L:AB1_
[error.82]
error=Texture MILVIZC310_LANDINGLIGHT_FRESNEL..DDS failed to load (FE_REQUEST_STATUS==13)
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
So after running through the whole process again I have been able to fix my radio problem it seems, but the cockpit back lighting is still not working properly.
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
So I ran the night light config from the Sim Objects and it says the MSVCP100.dll can not be found. How do I get that running. BTW, I got the radios fixed so that is good. Thank you guys for all your help.
-
- Posts: 1023
- Joined: Mon Sep 06, 2010 3:47 pm
Re: Another lighting issue... sorry (and Radios)
See here for how to get MSVCP100.dll reinstalled:Pilot_paul_r wrote: ↑Sun Apr 08, 2018 10:21 pmSo I ran the night light config from the Sim Objects and it says the MSVCP100.dll can not be found. How do I get that running. BTW, I got the radios fixed so that is good. Thank you guys for all your help.
https://social.technet.microsoft.com/Fo ... 0itproapps
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
See here for how to get MSVCP100.dll reinstalled:
https://social.technet.microsoft.com/Fo ... 0itproapps
[/quote]
Went through that process and still no joy. Bummer. So the problem is that the Milviz lighting service is not running? I made sure to have AV completely off, I got DX11, I have the proper redistributes, definitely running as Admin. I can’t think of what else could be going wrong. Sorry guys.
https://social.technet.microsoft.com/Fo ... 0itproapps
[/quote]
Went through that process and still no joy. Bummer. So the problem is that the Milviz lighting service is not running? I made sure to have AV completely off, I got DX11, I have the proper redistributes, definitely running as Admin. I can’t think of what else could be going wrong. Sorry guys.
-
- Posts: 19
- Joined: Tue Apr 03, 2018 1:50 am
Re: Another lighting issue... sorry (and Radios)
Do you guys think it is a LM problem with 4.2? Or is it a permission error so,ethereal that either I or my PC is creating? The only problem is the Milvis lighting system which is so frustrating cause no matter what I try nothing seems to work.
-
- Posts: 3446
- Joined: Sat Mar 13, 2010 7:38 pm
Re: Another lighting issue... sorry (and Radios)
The above solution is not quite what was needed for the cockpit lighting. You need to install this:
https://www.microsoft.com/en-za/downloa ... x?id=13523
https://www.microsoft.com/en-za/downloa ... x?id=13523