Jump to content

[FSX] Værøy X: All 3D scenery disappears.


Izomag

Recommended Posts

Hello,

 

I have some issue with Værøy X :( The scenery is loading correctly, but right after connecting to the VATSIM everything dissapeares, except people at the airport, and flat image of the island.

 

Here is SODE.log

Connection to VATSIM has been initiated at 21:07

Quote

[20:51:35.720] INFO  : Targetting Platform 'FSX'
[20:51:35.735] DEBUG  : Initializing Text Menus...
[20:51:35.735] DEBUG  : Initializing Seasonal Object Handler...
[20:51:35.735] DEBUG  : Initializing SimObject Lists...
[20:51:35.735] DEBUG  : Initializing QuadTree...
[20:51:35.735] DEBUG  : Initializing Sound Engine...
[20:51:35.829] INFO SODE.SOUNDENGINE : SoundEngine initialized.
[20:51:35.829] DEBUG  : Initializing Sim Bubble...
[20:51:35.829] DEBUG  : Initializing AI Monitor...
[20:51:35.829] DEBUG  : Initializing Jetway Handler...
[20:51:35.829] DEBUG  : Initializing VDGS Handler...
[20:51:35.829] WARN  : VDGS Pack is not found/installed!
[20:51:35.829] DEBUG  : Start Main Initialization!
[20:51:35.829] DEBUG  : Trying to read Settings from SimObjectsDisplayEngine.ini file...
[20:51:35.829] DEBUG SODE.SETTINGS : All Settings successfully read.
[20:51:35.829] DEBUG SODE.SETTINGS : CurrentSettings -> SoundEngine=1; WatchDog=1; UserJetwaySound=1;

SecMenuHotKey=SHIFT+VK_MINUS; AIDetection=0; AIJetwaySound=0
[20:51:35.829] DEBUG  : Trying to find Custom Configuration files...
[20:51:35.829] DEBUG SODE.XML : Finding SDX CFG Files...
[20:51:35.876] WARN SODE.XML : \cfg\ not found. Code(2) [C:\ProgramData\12bPilot\SODE\cfg\*.sdx]
[20:51:35.876] DEBUG  : Trying to build SimObject List out of Custom Config files...
[20:51:35.876] WARN SODE.XML : No SDX Files found! Lists are empty.
[20:51:35.876] DEBUG  : Trying to find XML Definition files...
[20:51:35.876] DEBUG SODE.XML : Finding XML Files...
[20:51:35.876] INFO SODE.XML : xml File Found: ENAT_SODE.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENAT_SODE_animation.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENAT_SODE_Clock_01.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENAT_SODE_Clock_02.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENAT_SODE_CL_VORE.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENAT_SODE_Terrain.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENVY_Flags_SODE.xml!
[20:51:35.876] INFO SODE.XML : xml File Found: ENVY_SODE.xml!
[20:51:35.876] DEBUG  : Trying to build SimObject List out of XML definition files...
[20:51:35.891] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\ENAT_SODE.xml'
[20:51:35.938] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml

\ENAT_SODE_animation.xml'
[20:51:35.938] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml

\ENAT_SODE_Clock_01.xml'
[20:51:35.985] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml

\ENAT_SODE_Clock_02.xml'
[20:51:36.016] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml

\ENAT_SODE_CL_VORE.xml'
[20:51:36.016] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml

\ENAT_SODE_Terrain.xml'
[20:51:36.047] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml

\ENVY_Flags_SODE.xml'
[20:51:36.047] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\ENVY_SODE.xml'
[20:51:36.078] DEBUG SODE.XML : XML Data successfully read and List created.
[20:51:36.078] DEBUG  : List generated! Trying now to insert into QuadTree...
[20:51:36.078] DEBUG  : QuadTree populated with SimObject references.
[20:51:36.078] DEBUG  : Trying to generate Aircraft Parameter Map from the INI file...
[20:51:36.172] DEBUG SODE.ACFTPARAMS : Door Parameters read for 26 ICAO Aircraft Types.
[20:51:36.172] DEBUG  : SDX/XML/INI Handling done! Start FS Processing...
[20:51:36.172] DEBUG  : Initializing Internal Sounds...
[20:51:36.172] DEBUG  : All Initialization Done!
[20:51:36.172] DEBUG SODE.FSPROCESS : Trying to connect to FS...
[20:51:36.188] DEBUG SODE.FSPROCESS : Connected to FS!
[20:51:36.188] DEBUG SODE.FSPROCESS : Secondary Text-Menu Hotkey set -> SHIFT+VK_MINUS
[20:51:36.188] DEBUG SODE.FSPROCESS : Setting up Connection Watchdog...
[20:51:36.188] DEBUG SODE.FSPROCESS : Entering FS Dispatch Loop.
[20:52:11.472] INFO SODE.FSLOOP : SODE connected to Simulator...
[20:52:11.545] DEBUG SODE.ACFTEXITS : No Custom Data Found for D:/Gry/Microsoft Flight Simulator

X/SimObjects/Airplanes/Aerosoft_DHC6_300_WHEEL/. Using original aircraft.cfg exit data!
[20:52:11.547] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\SimObjects\Airplanes\
[20:52:11.756] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\SimObjects\Rotorcraft\
[20:52:11.759] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\SimObjects\GroundVehicles\
[20:52:11.774] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\SimObjects\Boats\
[20:52:11.786] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\SimObjects\Animals\
[20:52:11.787] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\SimObjects\Misc\
[20:52:11.802] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in D:\Gry\Microsoft Flight Simulator X

\Addon Manager\Simobjects\Misc\
[20:52:11.814] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\12bPilot\SODE

\data\SimObjects\
[20:52:11.816] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\ProgramData\12bPilot\SODE

\SimObjects\
[20:52:11.816] INFO SODE.FOLDERMANAGER : SODE SimObjects Map Building completed. Size=64
[20:52:11.816] INFO SODE.FSLOOP : Successfull Registration of Reserved Key -> s Tab+S
[20:52:32.544] INFO SODE.FSLOOP : SeasonalObjectHandler: Variables initialized!
[20:57:03.894] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[20:57:05.922] INFO SODE.FSLOOP : ### FILTERING OBJECTS WITHIN SIM RADIUS OF 24000m
[20:57:05.923] INFO SODE.FSLOOP : ### Active SimObjects: 25; Active Wind Data Probes: 2
[20:57:05.940] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=31
[20:57:06.017] INFO SODE.FSLOOP :  + SimObject ENVY_Flags_SODE:ENVY Data Probe

[ENVY_Environmental_Data_Probe]. ID: 2
[20:57:06.017] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:ENVY Data Probe [ENVY_Environmental_Data_Probe].

ID: 3
[20:57:06.104] INFO SODE.FSLOOP :  + SimObject ENVY_Flags_SODE:ENVY_Flag_02 [ENVY_Flag_02]. ID: 4
[20:57:06.183] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Heliport_Pole_01 [ENVY_Windsock_Pole]. ID:

5
[20:57:06.183] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_Pole_03 [ENVY_Windsock_Pole]. ID:

6
[20:57:06.184] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_Pole_02 [ENVY_Windsock_Pole]. ID:

7
[20:57:06.184] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_Pole_01 [ENVY_Windsock_Pole]. ID:

8
[20:57:06.262] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:FX_Lighthouse [ENVY_FX_Lighthouse_01]. ID: 9
[20:57:06.340] INFO SODE.FSLOOP :  + SimObject ENVY_Flags_SODE:ENVY_Flag_01 [ENVY_Flag_01]. ID: 10
[20:57:06.557] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitA [ENVY_PLASI_Red_Pulsating]. ID: 11
[20:57:06.760] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitB [ENVY_PLASI_Red]. ID: 12
[20:57:06.853] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitC [ENVY_PLASI_White]. ID: 13
[20:57:06.926] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitD [ENVY_PLASI_White_Pulsating]. ID: 14
[20:57:06.927] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitA [ENVY_PLASI_Red_Pulsating]. ID: 15
[20:57:06.927] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitB [ENVY_PLASI_Red]. ID: 16
[20:57:06.928] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitC [ENVY_PLASI_White]. ID: 17
[20:57:06.928] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:UnitD [ENVY_PLASI_White_Pulsating]. ID: 18
[20:57:07.545] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:ENVY_Master_June [ENVY_Master_SP]. ID: 19
[20:57:07.627] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_01 [ENVY_Windsock_Calm]. ID: 20
[20:57:07.627] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_02 [ENVY_Windsock_Calm]. ID: 21
[20:57:07.628] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_03 [ENVY_Windsock_Calm]. ID: 22
[20:57:07.628] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Heliport_01 [ENVY_Windsock_Calm]. ID: 23
[20:57:54.964] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[20:58:54.977] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[20:59:54.955] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:00:54.984] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:01:54.972] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:02:54.965] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:03:54.974] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:04:54.970] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:05:55.015] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:06:55.139] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[21:07:13.471] INFO SODE.FSLOOP :  - SimObject ENVY_SODE:ENVY_Master_June [ENVY_Master_SP]. ID: 19
[21:07:13.471] INFO SODE.FSLOOP :  - SimObject ENVY_SODE:Windsock_Airport_01 [ENVY_Windsock_Calm]. ID: 20
[21:07:13.471] INFO SODE.FSLOOP :  - SimObject ENVY_SODE:Windsock_Airport_02 [ENVY_Windsock_Calm]. ID: 21
[21:07:13.471] INFO SODE.FSLOOP :  - SimObject ENVY_SODE:Windsock_Airport_03 [ENVY_Windsock_Calm]. ID: 22
[21:07:13.471] INFO SODE.FSLOOP :  - SimObject ENVY_SODE:Windsock_Heliport_01 [ENVY_Windsock_Calm]. ID: 23
[21:07:13.658] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_01 [ENVY_Windsock_Light]. ID: 48
[21:07:13.659] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_02 [ENVY_Windsock_Light]. ID: 49
[21:07:13.663] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Airport_03 [ENVY_Windsock_Light]. ID: 50
[21:07:13.664] INFO SODE.FSLOOP :  + SimObject ENVY_SODE:Windsock_Heliport_01 [ENVY_Windsock_Light]. ID: 51

 

I use other scenery with SODE (Seychelles v2) and everything is okay there.

Reinstalling SODE and Værøy X didn't help at all :(

 

 

Link to comment
Share on other sites

Well, in fact I've uninstalled the ENAT scenery long time ago. I have no idea why it still appears in SODE.

 

I had some issues with ENAT, but I don't remember exactly what kind of problems it was. Anyway I didn't try to fix it. I just gave up and promised to myself keep away from SODE.

 

But now I'm using Seychelles scenery, that also uses SODE, and everything works perfectly and stable. So I thought that I'll try with the Værøy X...

Link to comment
Share on other sites

  • Deputy Sheriffs

Without any more information it is hard to find the moment in the SODE log where you connected to VATSIM.

I would like to suggest that you delete the current log file, start your FAX and load into ENVY, then wait 5 minutes and then connect to VATSIM.

Afterwards you can attach the log file to your post (no need to copy it's content into your post). 

Also please give the exact time when you connected to VATSIM (according to your PC's clock).

Link to comment
Share on other sites

A new log is in the attatchment.

 

I connected to the VATSIM exactly at 23:10, according to my PC's clock.

3D scenery disappeared right at the moment when a weather has been loaded from the VATSIM server.

At 23:18 I disconnected from VATSIM.

Then I tried to reload the scenery (SHIFT+CONTROL+S), but nothing changed.

But when I've loaded default weather from FSX menu, 3D scenery of Værøy returned! So, it's the weather issue! :o

SODE.log

Link to comment
Share on other sites

  • Deputy Sheriffs

It sounds like a compatibility issue between SODE and Vatsim. In the past there where similar issues with GSX and SODE or APC and GSX. It has something to do, how they inject their data into sim.

Link to comment
Share on other sites

  • Deputy Sheriffs

From the log:

 

[23:07:04.562] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...

 

Is it possible that the VATSIM client sets your sim date/time to some values SODE doesn't recognize properly? 

What is your sim date/time before and after connecting to VATSIM?

 

Link to comment
Share on other sites

Quote

Are you running SODE 1.5.2? That Versions n includes also some fixes, that 1.4.2 doesn't have.

It sounds like a compatibility issue between SODE and Vatsim. In the past there where similar issues with GSX and SODE or APC and GSX. It has something to do, how they inject their data into sim.

 

I use the SODE version delivered with the scenery (Værøy and Seychelles). Today I've downloaded and installed SODE V1.5.2, but it didn't help.

 

Quote

Is it possible that the VATSIM client sets your sim date/time to some values SODE doesn't recognize properly? 

What is your sim date/time before and after connecting to VATSIM?

 

I've checked that time and date in FSX doesn't change after connecting to VATSIM.
Also the "Sync Zulu Time At Startup" in FS Copilot option is off.

 

Connecting to the VATSIM network itself doesn't cause vanishing of the scenery.
Scenery dissapeaes only if the weather has been downloaded from VATSIM servers. 

So, I think that the thing that trigger the scenery error in Værøy X is a weather.

 

BTW. The inbuilt Real World Weather in  FSX, doesn't cause the scenery in Værøy X to disappear.

 

Link to comment
Share on other sites

Hello,

 

Yes, every month is the same.

But during the winter months (november-februar), an ugly low-res 3D mountain remains in the middle of the island.

Link to comment
Share on other sites

  • Developer
vor 48 Minuten, Izomag sagte:

It's FSCopilot 1.7 and FSInn 1.3.

Sorry, unable to install that FSInn1.3 into my Win10 setup here...some ocx file needs a dplayx.dll from DirectX 6.1 (!).

 

Link to comment
Share on other sites

  • Developer

Can you verify that the model display correctly when you fly during night-time?
It looks like FSinn causes some trouble when SODE needs the metarvisibility variable to decide if the runway lights should be on or off during daytime.

Have you tried using a different client to log in to vatsim?

Link to comment
Share on other sites

  • Developer

Here's some new files that should solve the problem for now. Unzip it and replace the old files with the new ones.

The use of metar visibility in the model placement has been removed, since it looks like that's the variable being changed by FSinn when the model disappear.

 

Vaeroy FSinn fix.7z

Link to comment
Share on other sites

It seems like your patch fixed the problem. Thanks! :boingy_s:

However, I understand I've lost the feature of runway lighting at low visibility during daytime?

 

Answering earlier questions:

Yes, the scenery has been displayed correctly during the night-time... until the weather from VATSIM has been loaded.

I didn't try other VATSIM clients, because as far as I know, FSinn is the only VATSIM client able to load a real-world weather into the FSX.

 

BTW: I've also found old trash files of uninstalled scenery Alta X in SODE folder "C:\ProgramData\12bPilot\SODE\xml". Thanks again! :)

Link to comment
Share on other sites

  • Aerosoft
2 hours ago, 12bPilot said:

Sorry, unable to install that FSInn1.3 into my Win10 setup here...some ocx file needs a dplayx.dll from DirectX 6.1 (!).

 

 

Let's be clear on this, we do NOT support any compatibility with software that depends on Direct X versions that are 18 years old.

Link to comment
Share on other sites

3 hours ago, 12bPilot said:

Sorry, unable to install that FSInn1.3 into my Win10 setup here...some ocx file needs a dplayx.dll from DirectX 6.1 (!).

 

 

53 minutes ago, Mathijs Kok said:

 

Let's be clear on this, we do NOT support any compatibility with software that depends on Direct X versions that are 18 years old.

 

Strange. I'm pretty sure I'm running FSInn 1.3 with DirectX 11 on Windows 7 (64 bit).
I guess there is a problem with Windows 10 rather than DirectX itself.

Link to comment
Share on other sites

Archived

This topic is now archived and is 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