Weapon Delivery Planner released
-
Is MC compatible with U4?
they both use the same method to read the game data. -
@janjan I have no issues or problems using it!
-
@janjan said in Weapon Delivery Planner released:
Is MC compatible with U4?
they both use the same method to read the game data.Yes as cam/tac file structure hasn’t changed but both don’t support any L16 related data
-
@NIL said in Weapon Delivery Planner released:
@janjan I have no issues or problems using it!
there is however some issue.
Some training missions give an error while loaded in WDP.
Falcas apparently is not part of the BMS team anymore and repordetly refused to give access to the source code…
Anyway IIRC WDP is coded in VB…so… https://github.com/dnSpy/dnSpy -
@Virus I already did some RE on teh code a while ago to read BMS data to be used in my plugin.
I guess it is doable. The question is, is it worth it?
Will it be easy to adjust to 4.38? -
@janjan said in Weapon Delivery Planner released:
@Virus I already did some RE on teh code a while ago to read BMS data to be used in my plugin.
I guess it is doable. The question is, is it worth it?
Will it be easy to adjust to 4.38?It is worth in my opinion as WDP is an important piece in the workflow on many serious simmers here. Also, RE here is way easier than on a normal executable, being .NET completely readable (WDP seems also not obfuscated to me).
Easy to adjust to 4.38 is a question for BMS devs…I had some talk with them as I offered my experience (as beta tester for other flight sims) and my help as an IT guy for the DB migration, but for now it is not possible…I hope they will contact people like you and other guys who develop tools and app for BMS and give some head’up on what will change and what will be needed to adjust your “products” for 4.38.
On my end, I am still willing to help but I don’t want to waste time on unuseful things (maybe they are already doing something similar) or without help in understanding what’s going on under the hood. -
@Virus Agree
-
@Virus said in Weapon Delivery Planner released:
@janjan said in Weapon Delivery Planner released:
@Virus I already did some RE on teh code a while ago to read BMS data to be used in my plugin.
I guess it is doable. The question is, is it worth it?
Will it be easy to adjust to 4.38?It is worth in my opinion as WDP is an important piece in the workflow on many serious simmers here. Also, RE here is way easier than on a normal executable, being .NET completely readable (WDP seems also not obfuscated to me).
Easy to adjust to 4.38 is a question for BMS devs…I had some talk with them as I offered my experience (as beta tester for other flight sims) and my help as an IT guy for the DB migration, but for now it is not possible…I hope they will contact people like you and other guys who develop tools and app for BMS and give some head’up on what will change and what will be needed to adjust your “products” for 4.38.
On my end, I am still willing to help but I don’t want to waste time on unuseful things (maybe they are already doing something similar) or without help in understanding what’s going on under the hood.Yea it would be nice to have an idea of what’s planned. To me, WDP is a vital part of the ecosystem and gives better access to the DTC-side of the F16 systems. If there are substantial UI changes planned maybe that doesn’t become necessary, but without the ability to configure DTC and make kneeboards easily in the UI, there will always be a need for WDP.
-
@janjan said in Weapon Delivery Planner released:
@Virus I already did some RE on teh code a while ago to read BMS data to be used in my plugin.
I guess it is doable. The question is, is it worth it?
Will it be easy to adjust to 4.38?As we already have seen that there is a switch and a consolidation in terms of file formats mainly towards protobuf, I’d expect to get cam/tac and their relation to DB to be changes in the future as well.
I’d suggest use WDP MC as it is for now, will work for 4.37 and keep the feet still.
I’m pretty sure there will be valualbe enhancement in terms of interfacing with BMS for 3rd party devs in the future