Jump to content

How to check scenery integrity


FabioMagnoni

Recommended Posts

I use P3D v3.4 with hotfix 2.

 

I'm facing some crashes and related to CTD Guides and some research, they may be related to Scenery.

 

I already did a full clean install of my P3D v3.4 the only thing installed right now are my ORBX sceneries, nothing else. And I still have G3D.dll, Util.dll crashes.

The whole ORBX installation was over FTX Central V3 and my PC had to stay +4 days 24h on to download them all (Download was so slow), in some cases I turned on/off the CDN option while was downloading them.

 

How can I check if any of ORBX files are corrupted or missing? FTX Central only shows if they're installed or not.

 

Thanks

Link to comment
Share on other sites

On your P3D disk, look in the P3D folder.  In it you will see an Orbx folder, in it you should see a Troubleshooter.  Run it and you'll get a CMD line box and when finished, usually a few seconds you should see all green.  If you see any red it will send a file to your desktop telling you more information.  Good luck!

 

Orbx is awesome and you'll have this straightened out in no time.

Link to comment
Share on other sites

This is what I got in a Desktop File generated.

 

How do I fix it? 

 

Files requiring migration:
Ireland
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2an1.agn
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2fa1.bmp
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2hw1.bmp
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2lm1.bmp
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2m11.bmp
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2sp1.bmp
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2su1.bmp
    ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM\texture\063b2wi1.bmp
Wales
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2an1.agn
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2fa1.bmp
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2hw1.bmp
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2lm1.bmp
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2m11.bmp
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2sp1.bmp
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2su1.bmp
    ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM\texture\063b2wi1.bmp
--------------------
Invalid files:
ORBX\FTX_AU\FTXAU05_ROADS\Scenery\cvx_Orbx_Australia_Roads_SG-56_BRI.BGL
ORBX\FTX_AU\FTXAU05_ROADS\Scenery\cvx_Orbx_Australia_Roads_SI55_CAN.BGL
ORBX\FTX_AU\FTXAU05_ROADS\Scenery\cvx_Orbx_Australia_Railroads_S20-28_W.BGL
ORBX\FTX_AU\FTXAU05_ROADS\Scenery\cvx_Orbx_Australia_Roads_SF-SG-53.BGL
ORBX\FTX_AU\FTXAU18_CUSTOM\Scenery\500_LC_8637_Cooktown.bgl
ORBX\FTX_AU\FTXAU26_SHORES\Scenery\CVX_Orbx_Australia_Hydro_SG-56_BRI.BGL
ORBX\FTX_AU\FTXAU26_SHORES\Scenery\CVX_Orbx_Australia_Hydro_SH-56_ARM.BGL
ORBX\FTX_AU\FTXAU48_CUSTOM\Scenery\300_Melbourne_Poly.BGL
 

Link to comment
Share on other sites

Trying to use the Vector Auto Config it opens and exception window.

 

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: Cannot create a file when that file already exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.__Error.WinIOError()
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at FtxVector.Configurator.Ui.Forms.MainForm.Aec_AutoBtn_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FtxVector.Configurator
    Assembly Version: 1.35.0.0
    Win32 Version: 1.35.0.0
    CodeBase: file:///E:/Simulator/Lockheed%20Martin/Prepar3D%20v3/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8750 (QFE.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Link to comment
Share on other sites

Goodness me! (not what I was going to type:)) Fabio I am pretty sure that what you have written above is unintelligable to most of us, well me anyway. FAQ regarding Migration will sort out the problem. But allow me to precise:

1st, delete the .migration file which has generated to both ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM folder and  ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM folder. This will force a new migration process when you open Central and is likely to fix the migration problem for Ireland and Wales. If this does not work then you will have to uninstall Ireland and Wales and download a fresh install.

2nd, in respect of invalid files I can't help there but a look at FAQ's should have the solution as hundred's if not thousand's of customers have had the same experience.

Cheers  Dan

Link to comment
Share on other sites

On 1/15/2017 at 10:45 AM, Bassman said:

Goodness me! (not what I was going to type:)) Fabio I am pretty sure that what you have written above is unintelligable to most of us, well me anyway. FAQ regarding Migration will sort out the problem. But allow me to precise:

1st, delete the .migration file which has generated to both ORBX\FTX_EU\FTX_EU_IRL_08_CUSTOM folder and  ORBX\FTX_EU\FTX_EU_WLS_08_CUSTOM folder. This will force a new migration process when you open Central and is likely to fix the migration problem for Ireland and Wales. If this does not work then you will have to uninstall Ireland and Wales and download a fresh install.

2nd, in respect of invalid files I can't help there but a look at FAQ's should have the solution as hundred's if not thousand's of customers have had the same experience.

Cheers  Dan

Thanks that worked! for migration errors, ran the troubleshooter again and I got this file now

migration_missing.txt

Link to comment
Share on other sites

That is the original Invalid Files report that you got first time. As I say, I don't have the solution to that aspect however just do a search in the forum on "Invalid Files" and you will find a selection of solutions. One answer was that the Troubleshooter itself may be the problem with incorrect checksum process. I also note that whilst this query appears in a number of posts I could not actually find an answer coming from Orbx team??  Probably there, I just could not find it. Good luck with this one.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...