In T158488#2189210, @Sydney_Wolff wrote:

There is no requirement for the radar to be on to fire the sidewinder, it's firing and acquisition circuits are disconnected from the radar system, the radar track can be handed off to the missile seeker on later models, but it's not necessary for launch, it has it's own onboard sensors.

There is no requirement for the radar to be on to fire the sidewinder, it's firing and acquisition circuits are disconnected from the radar system, the radar track can be handed off to the missile seeker on later models, but it's not necessary for launch, it has it's own onboard sensors.

This is also true of the GM bicycle. I believe it's a consequence of bicycles having to use a semi-deprecated pre-PhysX vehicle class that dates back to, like, Arma 2. The GM devs have indicated it's not really fixable without BI themselves making some major changes to that vehicle type.

Thanks @veteran29 and @heyoxe, I'll take a look.

Can be seen happening in this recording I made: https://youtu.be/pD_eG_B7DiE?t=237 (starting soon after 3:58). Since recording this video I've spent more hours in the Slick and it is not an inevitable result of flying with a squad (or slingload), it is just requiring more careful inputs than I was making in the example video.

Its possible to resolve the loading of the Mod by following these steps on GeForceNow

Hi, this is an intended behavior, all vanilla campaigns are hidden by our menu.

In T158445#2188612, @Spoffy wrote:

I've passed this along, hopefully resolved soon!

The implementation was made at the request of the publisher.
Although it may seen counterintuitive it is one of the compromises that had to be made to have them available for players and mission creators.

I've passed this along, hopefully resolved soon!

It may be intended behaviour but not showing them in the Editor arsenal seems kind of counterintuitive

This is intended behavior, if you'd like the melee weapons to be available in the arsenal in your missions then add the following to your missions description.ext file
vn_arsenalShowMelee = 1;

Information about the issue has been passed on to the localization manager.

Thanks for the report, I'll have a poke around and see if I can see what's causing this issue.

If you make the change as I said and call your own function, just copy the BIS function and change that line, when the fix comes, it is just a case of find and replace the function name within your scripts. Just do it for the one mission. It doesn't affect the function in any other way, other than to make it compatible for the config entries for PF and also still works as normal for the vanilla units. I don't see how this cannot help?

Hi @VyMajoris , here is a sample config.cpp file with some documentation: https://gist.github.com/Heyoxe/8fbf1c769e9e3faf8c283ea0323aab36
This menu will be accessible via "Extras" >> "My custom menu".

Confirmed and seconded, please re-implement a more realistic solution.

Hope this is of use.

update: I appear to have solved the problem by opting out of the Steam client beta thing. Something about the newest beta update made Workshop services and server hosting not work properly in the game.

I also am unable to host servers (non-dedicated) with the DLC enabled. Re-downloading it now, but with the DLC enabled, can't host, with it disabled, I can host just fine. I suspect these errors are connected somehow.

I've experienced the same problem

Can confirm the issue happening as well while playing Mike Force where boats were not visible for the players.

Another suggestion from a nice man online I saw is to keep with the theme of the buttons, but not change their layout/positions. "like some paper that folds out when you go through the option"

I have found the issue. Using BIS_fnc_spawnGroup it creates an error on line 160 when using this command with the configfile entry. The issue is the fact that the config entry is different on the unit placement positions for the SOG groups. See below for OPF_F:

I'd also like to add that this error happens no matter what the contents of the mission are. Blank slate and fully made scenario give the same error.