ron533

OPF missing textures Hi, I'm playing Operation Piercing Fury campaign, with Mustang's latest terrain V1.18, and I get some missing textures, on bunkers and command posts for example. I suppose if it's original textures - it's not OPF's issue then. Known issue?? Thanks!!

HI, Still trying to finish the last mission...very hard with 2.5 engine and weather... Anyway, the briefing says Overlord radio is 262MHz, but it's still 251MHz. guessed it after it didn't work and since past missions were 251 for Overlord... Thank you for a great campaign! (The first campaign I bought!).

Won the bet :( Now I can't use the menus also in "stable". Guess ED really gets pissed by people with more than one monitor :mad:

Thank you Sicario for your fine work! I have a 4th monitor, non touch, that I wish to use for the AV-8B with Helios, but I have MFD cougar on the bottom of the monitor, not top as it is more comfortable and goes a long way back for me. I see I cannot change or adjust your profile to fit my monitor. Is there a way I can re-arrange it? I took an example from LOZ A10-C profile - where I can re arrange everything to my needs... Thanks!

I meant a BIP panel profile...but thank you anyway! :thumbup:

OK....thanks... Is it planned to make it available in DCS-BIOS anytime?

Hi, Does anyone have a BIP panel profile for the Harrier?? I couldn't find almost anything that works with it now... Thanks

Hi all, I've just bought the AV-8B , I'm using 3 monitors in surround and I want to export to my 4th monitor (not using Helios at the moment) found this thread and used the export files, but the fonts seems very thin and dark hardly readable. I've tried to play with the definitions lua for font size values but got weird results and no increase in brightness. How can I control it, if possible? is it a known issue? Many thanks for the support! Ron

Thanks, seems to be fixed! :thumbup:

Hi Artur, A small bug, In BIP panel I've cloned a task, which cloned ok, but when trying to edit its value(from 0 to 1 for example) , it also changes the original task value to 1. Thanks

I'm using BIP with DCS-BIOS. (And I already have the USB power management disabled).

Hi, Sometimes I cant get the panel working (BIP panel mainly) especially when alt tabbing or switching planes, and profiles. I try to close FP and run it again, reloading the profile ...but nothing. Only solution is to close DCS and run it again. Any correct order or things to do to make it run robustly in these situations? Thanks!

Thank you for the elaborate explanation. It sounds right and checks out as you described which is good enough of course... :) At first I thought you were explaining from what you BELIEVED is implemented rather than actually KNOW what is really implemented, for the cause of this. (also pointing me to what I misunderstood as the other direction - added to my confusion...) that is why I kept nagging about it... Nevertheless - your explanation seats well within scientific reason and should cover it. As I mentioned before, I would have expected from ED to add this basic information to the map (could be in the title bar), like every map which has this info... Cheers! :thumbup:

Hi, I'm attaching a combined picture to demonstrate my point better, sorry for the bad quality, but that's what I have right now at work... :) You can see the ruler (black line) from the Bullseye in Zugdidi area to the target area "Expected Offset" (the small unused airport). you get 170/40.57 , so in the offset from bullseye I typed 170.41 as seen in the CDU picture. And the markpoint was actually in the sea, a few miles to the West "Actual mission offset" as seen in the picture, which is wrong... opposite of what you calculated to be (to the East). If this is due to MagVar or something else is still not clear to me, and I have no clue in the map as to what offset should I consider or calculate to compensate for this deviation. That's why I expect to use the ruler and get the correct/corrected heading right away. Thanks :)

I see your point, but I would have thought the F10 map would already compensate for that... Also, the actual bulls of 170/40 gave me bulls more to the West, in the sea... don't have in front right now , but about 173+- and not 164 What is the MagVar of the PG map then? and why I don't see it happening there as well?...

I meant setting the offset after finding it with the ruler in the map. That doesn’t work well

? Bump... :smilewink:

Just found this: http://www.thedrive.com/the-war-zone/24741/new-3d-audio-will-allow-a-10-pilots-to-hear-alerts-come-from-the-direction-of-the-threat Could be a great mod here if possible!

Hi, Maybe it was reported before, but I couldn’t find it... I recently tried an offset from bullseye training which gave me a huge error using the F10 map in the Caucasus area. It did not repeat in the Persian Gulf map. For example, Bullseye is west of Zugdidi in a small island in the river by default, via the F10 map ruller I draw a line to the practice airfield below Kobuleti, The heading and distances is 170 for 40 miles. Offseting that in the CDU gave me the offest mission point west of the airfield,in the sea... way to far for the expected error. Hook from bulls in TAD - showed a correct Heading/Distance. As mentioned before, PG map was handling it fine. Is it known and reported? Any workarounds /fixes ? Thanks!

Hi Mustang, Thanks again for your hard work!! :thumbup: I wonder if there's any chance you would consider adding "Colored Roofs" to your great terrain, as in the obsolete but great mod by Cobac : https://forums.eagle.ru/showthread.php?t=168266 ?? Maybe as an optional addition to your mod? (if it would hurt slow machines) It makes the city so much more realistic looking and not as dull as it is in default now. It can also help coordinate attacks by pinpointing houses by their respective colors :music_whistling: Thanks again!! Ron

bump again...

I bet it will find itself in the next stable version once again :(

With 3 monitors and resolution of 6000 pixels, you need a wider FOV, or else your face is stuck in the HUD... It should be correlated to the viewport resolution, and adjustable accordingly. p.s. still no fix for this.

Thank you both, I will check your advice :thumbup:

OK, fair enough... :thumbup: Do you have any idea about my first question maybe?