This was with a brand new installation, with no cfg or anything carried over from 4.34, after tonight ill try and reinstall it again.

Hello, I installed the latest Weapons delivery planner - 3.7.17 build 164.

Upon first launch, I entered my Callsign matching bms, “OldGoat5”.

Upon further loading, I received a crash
“Conversion from string ‘Loading Callsign.ini’ to type ‘Integer’ is not valid.”

Here is the stack trace.

If I press continue or Quit and try again, WDP remains frozen and I cannot do anything.

Thanks,

OldGoat5

System info:
Win 10
BMS 4.35.2

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 "Loading Callsign.ini" to type 'Integer' 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.ToInteger(String Value)
   --- End of inner exception stack trace ---
   at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
   at WeaponDeliveryPlanner.clsLoadDTC.GetCallsignRadio(String fName)
   at WeaponDeliveryPlanner.clsLoadDTC.LoadCallsign(String fName, Boolean Version)
   at WeaponDeliveryPlanner.cntDTC.GetCampFile()
   at WeaponDeliveryPlanner.fclsMain.fclsMain_Load(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.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.8.4341.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
WeaponDeliveryPlanner
    Assembly Version: 3.7.17.164
    Win32 Version: 3.7.17.164
    CodeBase: file:///C:/Users/michael/Downloads/Weapon_Delivery_Planner_3.7.17.164/WeaponDeliveryPlanner.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4341.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
BMSUtils
    Assembly Version: 1.6.3.38
    Win32 Version: 1.6.3.38
    CodeBase: file:///C:/Users/michael/Downloads/Weapon_Delivery_Planner_3.7.17.164/BMSUtils.DLL
----------------------------------------
dbwdp
    Assembly Version: 1.6.0.2
    Win32 Version: 1.6.0.2
    CodeBase: file:///C:/Users/michael/Downloads/Weapon_Delivery_Planner_3.7.17.164/dbwdp.DLL
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
BMSLocation
    Assembly Version: 1.0.4.0
    Win32 Version: 1.0.4.0
    CodeBase: file:///C:/Users/michael/Downloads/Weapon_Delivery_Planner_3.7.17.164/BMSLocation.DLL
----------------------------------------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4330.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
LzssManaged
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/michael/Downloads/Weapon_Delivery_Planner_3.7.17.164/LzssManaged.DLL
----------------------------------------
LzssNative
    Assembly Version: 0.0.0.0
    Win32 Version: 
    CodeBase: file:///C:/Users/michael/Downloads/Weapon_Delivery_Planner_3.7.17.164/LzssNative.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></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.

Hello,

I have noticed in the latest versions of Falcon 4.34, the Bullseye calls are not being called by the AI in the regular modern convention. They used to be fine.

New format: One Three Four, Four three miles.
Convention + old format: One Three Four, Forty Three miles.

It is quite difficult to mentally keep track + memorize the new format, which is different from the modern military convention (please correct me if it has changed recently, from when I started and learned falcon the modern convention was, you pronounce the bearing as digits, and the mileage as a number).

Thanks for the work on Falcon all these years.

@Darkman:

IVC chapter 18 in the BMS-Technical-Manual was written by the ‘IVC specialist’ back in the 4.32 days. Obviously with newer Windows versions Microsoft has changed things to do with sound in Windows, so some options may not work like they used to.

Don’t forget to read the section on Outsiders on page 239. If you have it set to all your human AWACS will not be subject to the radio filter. If you have an AWACS flight in the TE/Campaign mission you would be better off perhaps to set Outsiders = awacs and have your human AWACS join BMS and select the AWACS flight to have the radio filter work as if he was in that jet in 3D, with all the radio sound effects such as distortion due to range etc.

Hi,

Does this mean the human AWACS who is in 2d, should also hear distortion radio effects? I haven’t been able to hear the effects as 2d awacs anymore.

Through the ivc shortcut i tried changing all options hiss etc everything, but i heard no change in ui when trying to be human awacs. All voices were without radio simulation.

I had same issue, even after restarting bms completely throttle didnt work.

Is there a way to restore this? It was a good way to stop the comms clutter from jets that are too far away from the zone that I care about.

Hi,

I am trying to be Human AWACS in the 2d UI. As AWACS, I cannot hear the Digital Signal Processing radio degradation sound effects anymore like in 4.33.

I have tried increasing the sound effects in the command line options but I still hear everyone clearly. I want to hear bad signal if players are too far away from the awacs, whose seat i have selected.

I have tried all of the /o options and changed /H etc but I hear no difference in 2d. I have also tried with no options but still no signal degradation.
“C:\Falcon BMS 4.33 U1\Bin\x86\IVC\IVC Client.exe” /c /k /s 123.123.123.14 /n OldGoat5 /u 363425 /v 141950 /q /t loop /H -10 /o awacs

Has this been removed from 4.34? Can anyone confirm radio degradation in 2D UI works for you?

Tried it and no issues during tonights flight night. I did not leave my pit though. I have been changing the default communication device a lot when I go into virtual reality, that may have been what was messing things up sometimes.

Hi.

In our wing flight nights, we have been noticing an IVC problem in campaigns after the newest update. The issue is that some of our pilots’ VHF radio will stop working for 1 or more pilots after maybe 20 minutes into the flight. The pilot it happens to can be random, but usually I am included. UHF still works, but we end up not realizing this till later. Sometimes both stop working. This may start happening when people disconnect and then reconnect back into the flight that has already taken off. When the problem occurs, some pilots can hear each other still but the pilot with the ‘broken radio’ cannot. Changing frequencies, and changing volume knob and trying to turn off and on the radio does not fix the issue.

Is this a known issue? I am on the latest BMS update and on Windows 7.