visibility criteria not applied in game for FMAPs generated by F4Wx
-
@suhkoi69 said in visibility criteria not applied in game for FMAPs generated by F4Wx:
in my last topic, I understood the interaction between Fog Altitude & Visibility criteria.
New fog feature is not implanted on FMAPS generated by F4wx : I noticed that all of FMAPs generated by F4Wx have a only the void map of fog ( where fog altitude is zero everywhere) …
So the consequence is that visibility maps are never applied in game with current FMAPs generated by F4WxIt shouldn’t be this way
F4Wx does not have fog elevation , normally bms
Detects that F4Wx uses an old version of Fmap and apply automatically a default fog altitude setting like 5000 ft or soThe mistake would be if F4Wx has incremented its Fmap file version without implementing the fog elevevation
-
One of the fmaps generated by BMS from a F4Wx fmap.
-
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
One of the fmaps generated by BMS from a F4Wx fmap.
So the last f4wx includes fog elevation right ?
-
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
One of the fmaps generated by BMS from a F4Wx fmap.
So the last f4wx includes fog elevation right ?
“Generated by BMS”. Loading a F4Wx fmap gives a global zero.
-
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
One of the fmaps generated by BMS from a F4Wx fmap.
I don’t understand « generated by bms from a f4wx «
-
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
One of the fmaps generated by BMS from a F4Wx fmap.
I don’t understand « generated by bms from a f4wx «
This is not a “10100.fmap” generated by F4Wx file. It’s a file generated while using F4Wx fmaps with MapsAutoUpdate enabled. This is a “mission cam” fmap file, generated by saving in BMS.
-
@LorikEolmin interesting ! I didn’t know…but does it only work for campaign ? Right?
-
@Mav-jp I only tried for TE in loading juste one FMAP file and no default fog value seemed me to be put while FMAP generated by F4wx had zero fog value everywhere ….
-
@suhkoi69 said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin interesting ! I didn’t know…but does it only work for campaign ? Right?
No…
-
@suhkoi69 said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@Mav-jp I only tried for TE in loading juste one FMAP file and no default fog value seemed me to be put while FMAP generated by F4wx had zero fog value everywhere ….
Sorry i don’t understand what you mean
-
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
One of the fmaps generated by BMS from a F4Wx fmap.
I don’t understand « generated by bms from a f4wx «
This is not a “10100.fmap” generated by F4Wx file. It’s a file generated while using F4Wx fmaps with MapsAutoUpdate enabled. This is a “mission cam” fmap file, generated by saving in BMS.
Have you opened the 10100.Fmap and compared it with the saved mission_name.fmap ?
-
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
One of the fmaps generated by BMS from a F4Wx fmap.
I don’t understand « generated by bms from a f4wx «
This is not a “10100.fmap” generated by F4Wx file. It’s a file generated while using F4Wx fmaps with MapsAutoUpdate enabled. This is a “mission cam” fmap file, generated by saving in BMS.
Have you opened the 10100.Fmap and compared it with the saved mission_name.fmap ?
As said earlier, “Loading a F4Wx fmap gives a global zero.”
-
@LorikEolmin totally agree …
Th FMAP is only read but no change is applied by BMS in game …it is still globally zero -
@suhkoi69 said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin totally agree …
Th FMAP is only read but no change is applied by BMS in game …it is still globally zeroI disagree.
EDIT: if you mean BMS doesn’t change the 10100 fmap, then of course not, unless you manage to save under that name (TE name 10100).
-
@LorikEolmin thanks a lot !
I tested and I confirm that FMAP is changed when it is saved under the TE name
On the other hand, it is interesting to know if FMAP is modified in Weather Commander (even with a minor change), BMS doesn’t apply any change and a global zero visibility will be on this new FMAP
-
As I said
The f4wx file does not include the fog elevation so this is normal you don’t have anything while reading it with weather commander
However when the game loads it , it should automatically sets the fog elevation to a default level.
That’s why you have it when the new Fmap is saved .
If you don’t have fog in game then this is where the bug is.
———
If you want to have fog elevation in the Fmap generated by f4wx, contact Ahmed
-
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
As I said
The f4wx file does not include the fog elevation so this is normal you don’t have anything while reading it with weather commander
However when the game loads it , it should automatically sets the fog elevation to a default level.
That’s why you have it when the new Fmap is saved .
If you don’t have fog in game then this is where the bug is.
———
If you want to have fog elevation in the Fmap generated by f4wx, contact Ahmed
You said default level is “5 000 feet or so”. It’s not one number, as the pic shows.
-
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
As I said
The f4wx file does not include the fog elevation so this is normal you don’t have anything while reading it with weather commander
However when the game loads it , it should automatically sets the fog elevation to a default level.
That’s why you have it when the new Fmap is saved .
If you don’t have fog in game then this is where the bug is.
———
If you want to have fog elevation in the Fmap generated by f4wx, contact Ahmed
You said default level is “5 000 feet or so”. It’s not one number, as the pic shows.
This makes absolutely no sense at all
-
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@LorikEolmin said in visibility criteria not applied in game for FMAPs generated by F4Wx:
@Mav-jp said in visibility criteria not applied in game for FMAPs generated by F4Wx:
As I said
The f4wx file does not include the fog elevation so this is normal you don’t have anything while reading it with weather commander
However when the game loads it , it should automatically sets the fog elevation to a default level.
That’s why you have it when the new Fmap is saved .
If you don’t have fog in game then this is where the bug is.
———
If you want to have fog elevation in the Fmap generated by f4wx, contact Ahmed
You said default level is “5 000 feet or so”. It’s not one number, as the pic shows.
This makes absolutely no sense at all
We’re talking about BMS. It’s not always supposed to make sense.
-
ok i investigated this
There is ABOLUTLY no bug at play here
The F4WX does not countain any fog altitude information, therefore when the F4WX is read by BMS at loading a map, the Fog altitude per default for each cell is the Cumulus Layer Alitude
that means the fog visibility will apply fully below cmulus (that was the old styl anyway).
i checked in game, by loading a F4WX native directly i do have specified fog visibility under cumulus as it should be
At that stage, if you open a F4WX native with WC , it wont show the fog altitude as WC does not automatically set up the fmap missing info.
When you save the TE / cam in BMS though, the newly generated copy of the F4WX fmap will include those fogZ altitude (cumulusZ layer per default) and that’s what you see afterward when you load this newly saved fmap with WC
no bug at all