I just finished listening to it. Many thanks to I-Hawk and MaxWaldorf for all these great insights. Chapeau! Also I highly appreciate the recent transparency.
Latest posts made by EggsNFries
-
RE: Update on 4.35 U2
-
RE: Update on 4.35 U2
Is there any chance to check out that podcast again for anyone who missed it (like me)? I did a quick google search but could not find it.
-
RE: Map view during flight
A moving map has nothing to do with RTT as you wonāt need any information from RTT to make a moving map with external tools.
Im currently running Helios with ICE profile which has a moving map includedCool, nice to know. Does your Helios application also show all of the HSD symbology; so is it some kind of overlay of some sort?
-
RE: Map view during flight
You mean something like a moving map which is shown in some external tool or even on the HSD? This has been discussed thoroughly multiple times already on the forums and nothing similar has emerged yet. But maybe once the current problems with RTT export are fixed (maybe in the upcoming 4.35.1 release?) something could be possible. Maybe here in the future: https://www.benchmarksims.org/forum/showthread.php?41013-New-free-MFD-ICP-app-to-control-Falcon-BMS-from-touch-devices
-
RE: EZBoards - Generate kneeboards (flights, comms, stpts, weather) from briefings
Thank you Logic for your tool - it looks like a nice addition to WDP. I just gave it a go, but it crashes as hostfxr.dll seems to be missing (see the screenshots for details). The batch script actually keeps running and finally generates a dds file that contains only blank pages. The blank dds is eventually moved to KoreaObj too.
-
RE: F4Wx ā Real Weather Converter
IIRC, grb2fmap is the piece of software Ahmed made first and from which F4Wx emerged from. It hasnāt been updated since 2016 and is probably not compatible with 4.35ā¦ not even with 4.34 I assume.
-
RE: Really stupid iff question
Ehmā¦ FCR off? Maybe you missed switching it on after its initial BIT?
-
RE: Inconsistency FMAP & weather briefing
Hello,
I tested the mission with Sukhoi69. I downloaded the TE mission files including the fmap files. I edited the TE in game, by selecting the strike1 mission, clicking the EDIT button in the UI. I clicked on the WEATHER button, then I chose Map model in the āWeather modelā choice. I loaded strike1.fmap by selecting it in the list and by clicking SAVE WTH.
Then I exited the editor, I tried to commit in the TE. I opened the briefing and I searched for the weather information. I had Poor Poor Poor with visibility values of 17km 0km 17km for the Take Off, Target and Landing areas.
I exited the TE mission schedule and re-opened the strike1 TE in the editor to reload the weather strike1.fmap in the weather model. Then I clicked the Back button to recommit one more time in the TE. When I loaded the briefing, I had different values in the weather information : Sunny Fair Sunny with 60 km of visibility for all three areas. Those values are quite different from the first I had !
I tried several times the same steps of reloading the strike1.fmap in the TE editor, and then recommitting in the TE to see the brief and I obtained those values :
āPoor Poor Poor with 0km 15km 0km of visibilityā
The other try gave me " Sunny Sunny Sunny with 60km 60km 60km".It seems to be quite surprising to get that range of possibilities in the obtained weather data.
What youāve been describing feels reminiscent to what I experienced a couple days ago. Itās probabily unrelated to the OP, but maybe not ā¦
I was playing around with fmaps in 4.35, testing FPS numbers. I created a test flight using current weather which I downloaded using F4Wx. And usually I restart BMS after exiting any flight, whether its a TE or a campaign flight. And doing so invoked the weather being as reported by F4Wx and the briefing. However, after being somewhat fed up by constantly restarting BMS, I started doing subsequent flights. Interestingly, the weather went all clear with 50km+ visibility, instead of being stormy overcast, after reloading my TE for the second time. What struck me most is that I can reproduce that observation in the TE_BMS_00_Benchmark_Test TE as well. Jumping into the cockpit for the first time after starting BMS brings up inclement weather as it should be. Leaving the cockpit, closing the TE and reloading the TE and joining the flight again without restarting BMS invokes sunny weather, however. Butthe rain is still there ā¦ See the screenshot enclosed.
-
RE: Weapon Delivery Planner released
Hi Falcas! Thank you very much for the update and all your efforts. I just gave the new version a go, but it crashes everytime I try to load a campaign or any TE file.
Hereās the crash log:
System.IO.FileNotFoundException: Die Datei oder Assembly āLzssManaged, Version=1.0.0.0, Culture=neutral, PublicKeyToken=nullā oder eine AbhƤngigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
Dateiname: āLzssManaged, Version=1.0.0.0, Culture=neutral, PublicKeyToken=nullā
bei WeaponDeliveryPlanner.fclsMain.GetTheater()
bei WeaponDeliveryPlanner.fclsMain.LoadTE()
bei WeaponDeliveryPlanner.cntDataCard.OpenFile(String fName)
bei WeaponDeliveryPlanner.cntDataCard.OpenMission()
bei WeaponDeliveryPlanner.fclsMain.mnuOpenMission_Click(Object sender, EventArgs e)
bei System.Windows.Forms.MenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.MenuItem.MenuItemData.Execute()
bei System.Windows.Forms.Command.Invoke()
bei System.Windows.Forms.Command.DispatchID(Int32 id)
bei System.Windows.Forms.Control.WmCommand(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.Form.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)WRN: Protokollierung der Assemblybindung ist AUS.
Sie kƶnnen die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler fĆ¼hrt zu einer gewissen LeistungseinbuĆe.
Sie kƶnnen dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4311.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
ā--------------------------------------
WeaponDeliveryPlanner
Assembly-Version: 3.7.16.152.
Win32-Version: 3.7.16.152.
CodeBase: file:///D:/sims/tools/WDP/WeaponDeliveryPlanner.exe.Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 14.8.3761.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.4311.0 built by: NET48REL1LAST_B.
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.4311.0 built by: NET48REL1LAST_B.
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.4290.0 built by: NET48REL1LAST_B.
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.3761.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.3761.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.3761.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.33.
Win32-Version: 1.6.3.33.
CodeBase: file:///D:/sims/tools/WDP/BMSUtils.DLL.Microsoft.VisualBasic.resources
Assembly-Version: 10.0.0.0.
Win32-Version: 14.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/v4.0_10.0.0.0_de_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll.System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.System.Data
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4290.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll.System.Data.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Data.resources.dll.System.Transactions
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll.System.EnterpriseServices
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll.System.Numerics
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll.dbwdp
Assembly-Version: 1.6.0.0.
Win32-Version: 1.6.0.0.
CodeBase: file:///D:/sims/tools/WDP/dbwdp.DLL.BMSLocation
Assembly-Version: 1.0.4.0.
Win32-Version: 1.0.4.0.
CodeBase: file:///D:/sims/tools/WDP/BMSLocation.DLL.mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.System.Web
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4261.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.************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.Zum Beispiel:
<configuration></configuration>
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt. -
RE: Restore kneedboard 4.35
Please refer to section 8.8. in the BMS Technical Manual in your docs folder. There youāll find all the details you need.
Page 8-60: āIt is therefore recommended to backup the default 7982 to 7997 DDS files from your \Data\TerrData\Objects\KoreaObj folder to ensure you can restore them whenever needed.ā