Jump to content
The simFlight Network Forums

TOPER Tool (Boeing 777) - Support

nixdevelopment
 Share

Recommended Posts

  • Replies 143
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Posted Images

bayle Newbie

bayle

Posted
Posted

Somebody can help me ,I bought Topper Boeing B 777 it does not work  i get :

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


************** Exception Text **************
System.InvalidCastException: Conversion from string "208.8" to type 'Double' is not valid. ---> System.FormatException: Input string was not in a correct format.
   at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   --- End of inner exception stack trace ---
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value)
   at PerformanceCalculatorTemplate1.Form1.btnCalc_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: 4.0.0.0
    Win32 Version: 4.0.30319.18052 built by: FX45RTMGDR


----------------------------------------
TOPER B777
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0


----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50709.17929 built by: FX45RTMREL


----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18044 built by: FX45RTMGDR


----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL


----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR


----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18021 built by: FX45RTMGDR


----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL


----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR


----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR


----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL


----------------------------------------


************** 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.
 
 Thank you for your help Eric
Link to comment
Share on other sites
bayle Newbie

bayle

Posted
Posted

Hellow ,i get windows 7 ,Net framework 4.5 i try running as administrator...I reinstall Toper the same bug appears  when i finish to install ":unable to execute file : E:\Program files(x86)Toper calculator B 777Toper B 7777.exe create Process files: code 740 l'opération necessite une élévation " thanks for help Eric

Link to comment
Share on other sites
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

Windows is in french language and Toper crashes on start up it does not load all ...

Thank you for the info, I will look into it in the following couple of days and will get back to you with the solution. In the meanwhile as an alternative you could try and change your windows Regional settings to U.S. as a temporary solution until I resolve the issue.

Thank you for your patience

Link to comment
Share on other sites
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

Dear Eric,
 
please download the TOPER 777 v1.0.1 Beta version update:

  • copy the downloaded file to the TOPER 777 installation directory (where TOPER B777.exe is located)
  • run the 'TOPER B777_v1.0.1beta.sfx.exe' file - the files get extracted automatically 

After applying the patch TOPER splash window should say: 'v1.0.1 beta'

 

Please let me know if this solved your problem.

Link to comment
Share on other sites
bayle Newbie

bayle

Posted
Posted

Thanks for your help but :no success

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


************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'E:\Program Files (x86)\TOPER Calculator Tool\data\wndcor.dat'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   at System.IO.StreamReader..ctor(String path)
   at PerformanceCalculatorTemplate1.Form1.btnCalc_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: 4.0.0.0
    Win32 Version: 4.0.30319.18052 built by: FX45RTMGDR


----------------------------------------
TOPER B777
    Assembly Version: 1.0.1.0
    Win32 Version: 1.0.1.0


----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50709.17929 built by: FX45RTMREL


----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18044 built by: FX45RTMGDR


----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL


----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR


----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18021 built by: FX45RTMGDR


----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL


----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR


----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR


----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL


----------------------------------------


************** 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
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

Dear Eric,

Sorry to hear that it is still not working properly. Are you at least able to load TOPER after the update? Does the error occur on startup or after you press the 'calculate' button?

Also please make sure that the EXE file itself is in 'B777' folder: the debug error doesn't show it-perhaps that is what makes it crash.

Link to comment
Share on other sites
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

am i the only with the problem  ?

Dear Eric,

 

so far the only thing causing issues is that your Windows is in French. Can you please answer my previous two questions, so I can understand better what is going on and rectify the problem:

  • Are you at least able to load TOPER after the update?
  • Does the error occur on startup or after you press the 'calculate' button?

​Thank you for your cooperation

Link to comment
Share on other sites
zaharevgen Newbie

zaharevgen

Posted
Posted

Hi! I have the same problem!

 

Подробная информация об использовании оперативной 
(JIT) отладки вместо данного диалогового 
окна содержится в конце этого сообщения.


************** Текст исключения **************
System.InvalidCastException: Приведение строки "272.4" к типу "Double" является недопустимым. ---> System.FormatException: Входная строка имела неверный формат.
   в Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
   в Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   --- Конец трассировки внутреннего стека исключений ---
   в Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)
   в Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value)
   в PerformanceCalculatorTemplate1.Form1.btnCalc_Click(Object sender, EventArgs e)
   в System.Windows.Forms.Control.OnClick(EventArgs e)
   в System.Windows.Forms.Button.OnClick(EventArgs e)
   в System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   в System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   в System.Windows.Forms.Control.WndProc(Message& m)
   в System.Windows.Forms.ButtonBase.WndProc(Message& m)
   в System.Windows.Forms.Button.WndProc(Message& m)
   в System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   в System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)




************** Загруженные сборки **************
mscorlib
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1008 (RTMGDR.030319-1000)


----------------------------------------
TOPER B777
    Версия сборки: 1.0.0.0
    Версия Win32: 1.0.0.0


----------------------------------------
Microsoft.VisualBasic
    Версия сборки: 10.0.0.0
    Версия Win32: 10.0.30319.1 built by: RTMRel


----------------------------------------
System
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1001 built by: RTMGDR


----------------------------------------
System.Core
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.233 built by: RTMGDR


----------------------------------------
System.Windows.Forms
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1002 built by: RTMGDR


----------------------------------------
System.Drawing
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1001 built by: RTMGDR


----------------------------------------
System.Runtime.Remoting
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1 (RTMRel.030319-0100)


----------------------------------------
System.Configuration
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1015 (RTMGDR.030319-1000)


----------------------------------------
System.Xml
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1015 built by: RTMGDR


----------------------------------------
System.Windows.Forms.resources
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1 built by: RTMRel


----------------------------------------
mscorlib.resources
    Версия сборки: 4.0.0.0
    Версия Win32: 4.0.30319.1 (RTMRel.030319-0100)


----------------------------------------
Microsoft.VisualBasic.resources
    Версия сборки: 10.0.0.0
    Версия Win32: 10.0.30319.1 built by: RTMRel


----------------------------------------


************** Оперативная отладка (JIT) **************
Для подключения оперативной (JIT) отладки файл .config данного
приложения или компьютера (machine.config) должен иметь
значение jitDebugging, установленное в секции system.windows.forms.
Приложение также должно быть скомпилировано с включенной
отладкой.


Например:


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


При включенной отладке JIT любое необрабатываемое исключение
пересылается отладчику JIT, зарегистрированному на данном компьютере,
вместо того чтобы обрабатываться данным диалоговым окном.
Link to comment
Share on other sites
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

 

Hi! I have the same problem!...

 

Dear Evgeny,

 

have you tried updating to TOPER 777 v1.0.1 Beta version? 

The problem comes from your Windows (like Eric's) not being in English language. I will try my best to sort this issue out in the nearest future.

 

Thank you for your patience and apologies for the inconvenience.

Link to comment
Share on other sites
zaharevgen Newbie

zaharevgen

Posted
Posted

Dear Evgeny,

 

have you tried updating to TOPER 777 v1.0.1 Beta version? 

The problem comes from your Windows (like Eric's) not being in English language. I will try my best to sort this issue out in the nearest future.

 

Thank you for your patience and apologies for the inconvenience.

Hi! Tried beta version ... All is well! Thank you.

Link to comment
Share on other sites
  • 1 month later...
ramon.cutanda Newbie

ramon.cutanda

Posted
Posted

Hi,

 

TOPER is EXTREMELY buggy. I can get the performance data in some airports but sin some others is completely impossible. I get a hateful "Unhandled exception" "Index was outside the bounds of the array" most of the times. What about a HUMAN description of the error so that we may know what is wrong?  Using a database of the airports is very handy because we only have to input the ICAO code to get the data. But what about when a runway changes its number due to magnetic variation? How can we possible know we are inputting an inexistant number in the database? What if we use an airport not included in the database? I'm thinking for example in ZULS Lhasa Gongar (Tibet) which is not included in FSX by default. Maybe for those cases it could be useful to manually input the information of the runway, as in the first version. So, if I get one of those dreaded "Unhandled" erros I could manually input the runway data and make sure it's not a database mistake.

 

Next you'll find the description of the error when using this input information:

ARPT: KDEN

RWY: 35R

INTX:

COND: DRY

WIND: 360/11 KT

OAT: 5 ºC

QNH: 2991 HPa

Takeoff Weight: 192598 KG

Boeing 777-200ER/GE90-90B

 

NOTE: I've tried versions 1.0, 2.0 beta, 2.0.2 and 2.0.3

 

Error:

---------------------------------------------------------------------------------------------------

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

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at PerformanceCalculatorTemplate1.Form1.btnCalc_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: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
TOPER B777
    Assembly Version: 2.0.3.0
    Win32 Version: 2.0.3.0

----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50938.18408 built by: FX451RTMGREL

----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
System.Windows.Forms.resources
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------
mscorlib.resources
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL

----------------------------------------

************** 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.


---------------------------------------------------------------------------------------------------

Thanks for the support

Link to comment
Share on other sites
ramon.cutanda Newbie

ramon.cutanda

Posted
Posted

I found the cause of my error. I was entering mercury inches in the QNH instead of HPa.... Doh!!!

 

DOH-Homer-350x196.jpg

 

But even if it was my error, what about a "nice" and "polite" warning of the type: "The input is out of range. Please, check you are introducing HPa and not mercury inches" instead of the "ugly" unhandled errors?

 

 

Bests,

Link to comment
Share on other sites
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

...How can we possible know we are inputting an inexistant number in the database? What if we use an airport not included in the database? I'm thinking for example in ZULS Lhasa Gongar (Tibet) which is not included in FSX by default. Maybe for those cases it could be useful to manually input the information of the runway, as in the first version.

 

I have checked the 'ZULS' airport and it is included in the current database (airport database that comes with 'TOPER' is independent of the FSX and includes most of world airports). 

 

Please download the v2.0.4 from the update section.

 

Thank you for your feedback.

Link to comment
Share on other sites
  • 9 months later...
Cristian Calvillo Newbie

Cristian Calvillo

Posted
Posted

Hello, I have a few problems with the calculated performance for 777-200LR and 777-300ER (PMDG ), I mean in certain circumstances like a high airport as MMMX the calculations for TO and derate temperature seems to be excessive, maybe TOPER Tool is not taking in consideration the CLIMB gradient limit and only is taking the limitation for runway length. the result of this, it's a over derated take off's with a high speed rotation with a poor climb gradients with no more than 10 degrees of pitch for avoid the stall speed, this is not normal with 30 tons less than the PMTOW, any idea?

 

 

Regards

Link to comment
Share on other sites
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

Dear Christian,

 

are you using DE-RATE and ASSUMED TEMPERATURE methods at the same time? 

 

200LR and 300ER types have massive engines and are in general not climb limited due to shear power of the power-plants. If you have issues with climb performance, try using lower flap settings like flap 5. This will extend the takeoff roll but improve climb performance.

 

Also please provide me with some examples, so I can make sure there is not a major bug in the system.

 

Regards,

 

Nikola 

Link to comment
Share on other sites
  • 2 months later...
nixdevelopment Contributor

nixdevelopment

Posted
  • Author
Posted

Hi,

 

I really like this application.

 

The only issue is that i use this on a Windows 8 tablet and i cant get it to maximize to full screen.Also is there any way that the text can be enlarged as its a bit hard to see on a 8" screen.Thanks.

 

Clinton Fernandes.

 

Dear Clinton,

 

welcome to the forums. Could you send me a screenshot of how TOPER looks on your tablet? I can perhaps fix it, so it fits the screen. Also I will be implementing text re-sizing feature in the next update.

 

Regards, 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.

  I accept