mkiii

As mentioned above, changing the following in Mods\Aircraft\F-16CzCockpit\Scripts\materials.lua aught to help:- materials["HUD"] = {2, 255, 20, 200} EG. This is much yellower & (in theory) more opaque: {200, 255, 20, 255} There is a Mod available that also does this if you want to use OvGMe, which saves you having to set it all up yourself. https://www.digitalcombatsimulator.com/en/files/3306470/ I haven't tried it myself, so I can't verify that it still works. I have no problem reading the standard HUD against the Sun, Clouds & so on, but do have problems against the haze of the Horizon in the default Free Flight in the Caucasus mission. Perhaps that is akin to your overcast situation. {EDIT} Now having tried a flight exactly as you described - I agree, the HUD is very faint to the point of unreadability. Whether that is realistic or not I don't know. The yellow colour mentioned above does make it a bit clearer though. Note that the HMCS Symbology is done elsewhere, so you can compare the original green with any new colour by turning it on.

As I keep saying, the engine was running normally. Nuff said. Out...

Manafacturing must have become shoddy since the 80s then.

I may be wrong. I haven't been near an F-16 since the late 80s. However, I think you are also misinterpreting what I wrote. 1st: I don't recall saying anywhere that there was a separate "Hydrazin motor". 2nd: OK I hands up I misstyped LP Bleed air & forgot to edit it to say HP. 3rd: I bow to your greater knowledge, although, being a petty individual I must point out that it is Hydrazine with an e - the light caption is abbreviated. ;) 4th: Isn't that what I said? 5th: I did say more than once that the engine was running normally, not shut down or windmilling & I don't recall saying that there was a separate "Hydrazine motor". I'll give you a win because I'm really not that concerned, although it would be interesting to hear from someone who has used the EPU in the air with a running engine.

If it turned off the instant your wheels touched down, it would make stopping the aircraft very interesting - and involve the barrier - not really a good idea in something with no canopy frame to hede behind ;) Also it would have meant all the Hydrazine emergency drills we did in Germany in the 80s with full NBC gear were a waste of time.

Yes, but the EPU would use bleed-air from the still running engine LP compressor rather than sparking up the Hydrazine motor... Hydrazine bad! Either way, and somewhat OT, the engine does not shut off, nor does the epu start properly - in the current release. I assume it is still WIP. The green run light illuminates when you move to battery power or turn it off, and both the Hydrazine AND Air lights illuminate. Only the Air light should come on. The HUD should be powered by the EPU in the F16C. It isn't in this build if the power is switched to battery. That may be wrong - but I'm not 100% sure. It does power the HUD if the power switch is left alone but the engine shut down. So I'm unsure whether this is the case if there is only battery power - but that is sort of the point of the EPU - that and Hyd power, but in the event of no engine, you would fire up the JFS to keep the engine spinning at 20% to make sure that the life of the emergency power is extended.

The panels on the upper fuselage should be flush with the skin. They currently have a pronounced bump/normal map applied. Other than skin reinforcing plates that are not modelled or in the current texture, this area should be pretty smooth. The real jets can have a lot of staining around the joints which might make them appear to be raised , but they are not afaik.

Turning the Main Power to Off certainly doesn't stop the engine. So did we find out why a keybinding to soemething that cannot shut the engine down does so, or was it just finger trouble after all, and a throttle left in the closed position?

Uncaging works for me, but I had to read the "tooltip" to find out how. However, the title of the thread is Unable to CAGE not UNCage. I cannot Cage it again once it is uncaged either - not that it is stopping me flying, but it is not working as it should.

I don't think anyone here is suggesting that all EDs attention be assigned to improving graphics quality, or comparing DCS to some cheap VR crap, but they are saying that in recent builds the performance they HAD before was much higher than it is now. It did get to a stage where I could use VR with some lowering of settings on my PC, but in the last couple of updates, even in Non VR mode, with settings turned down much lower than they were a couple of months ago, I'm getting about 2/3 the framerate, so does that not suggest that there is a problem somewhere, and not just in achieving a decent VR framerate?

"Off" doesn't mean retract, it means "stop opening/closing". It is the neutral position of the 3 position HOTAS Switch. I can't see why it even has a keystroke assigned, since just not pressing Open or Close = OFF.

What a PITA. Next time, can't you just check for FC3 before doing this?

Things look different, in different lighting conditions & with different maps & different settings etc. People aren't always specifying when & where they are flying. In the Caucuses map freeflight mission: I did notice that with regard to the button lighting that across the board, the AP lights are now a lot clearer. The Turn to Target & other buttons on that panel are extremely hard to see unless in complete shadow with English cockpit selected. They seem a tiny bit clearer in the Russian cockpit & no easier to see when not in shadow on other maps. Harder in fact, because glare is an issue. Try Normandy Free Flight mission. Shadow settings flat or otherwise make no difference to me at least. Either way, I didn't pay for it, nothing seems worse than before, and there are improvements. Zooming in to an instrument panel so close that individual polygons & pixels show up is not something I can complain about - so I won't. The line has to be drawn somewhere, and I'd rather have 2d needles in my instruments than something that is a beautiful slideshow. It certainly looks more realistic than it did imo.

Polish aircraft at least seem to be still using the original instrumentation (cryllic & metric) http://www.primeportal.net/hangar/luc_colin3/su-22m4_fitter/index.php?Page=3 Although I'm sure that I glimpsed the word "Feet" on a climb & dive indicator in a Polish Mig-29

Just for the record. try SP A10-C Insta mission - Free Flight, (no weather), and formate on your AI wingman. crossing his rear quarter makes your wing dip at least 30 to 45 degrees if you are within a couple of aircraft lengths. This seems to be a bit extreme IMO.

Nope. Every source says 8x12", and that size fits 3x into the cockpit of an old 3d model I made when this was first designed. This is the outer dimensions not the screen size. However, if you don't believe me, or Wikipedia, then maybe the Pakistan Air Force Handbook is good enough? If you think Wiki is wrong, please go & correct it. https://books.google.co.uk/books?id=CYqnBQAAQBAJ&lpg=PA80&ots=7crsGh7xvR&dq=mfd%20used%20by%20jf17&pg=PA80#v=onepage&q=mfd%20used%20by%20jf17&f=false

20.3 cm (8.0 in) wide and 30.5 cm (12.0 in) tall according to Wikipedia.

Never mind how to drop bombs (press the red button). What concerns me is that "Brake" is mispelled as "Break" throughout the guide. That I can never forgive...

I don't remember the sea looking thaty clear, even in the summer. One thing this map will not suffer from is tree related framerate issues.

Bit late to reply, but if you just change try_find_assigned_viewport("AJS37_TV") to:- try_find_assigned_viewport("AJS37_TV, LEFTT_MFCD") Then you can manage without a specific entry in the Monitor config file for the TV, since it will default to using the LEFT_MFCD entry along with the RADAR. To make the TV display look a bit better, you can edit the base_page.lua and delete/comment out the entire section from about line 18 :- clip_mesh_verts = {} ... to the end of the loop starting around line 36:- "for i = 1,number_of_triangles do... end" This section seems to draw the black mask. I can't figure the way that the rgb channels are un-aligned, but it's a start.

The config looks ok, but you need to edit some lua files to get these extra doodads to actually export. Look in DCS World Install folder for Mods/aircraft/A-10C/Cockpit/scripts/ You will see folders for AN_ALR69V, CDU, CMSC,CMSP,DigitalClock,MFCDx,UHFRadio etc AN_ALR69V as an example Add the following red text at the top of the /Indicator/AN_ALR69V_init.ua file:- dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON purposes = {render_purpose.GENERAL} update_screenspace_diplacement(1,0,0) try_find_assigned_viewport("ED_A10C_RWR","RWR_SCREEN") ---------------------- rwr_symbols_bound = 0.027 -- coeff to limit indication on RWR when symbol can't be place on RWR entirely -------PAGE IDs------- Do the same for the other files mentioned, but change the names being exported to the desired instrument thus:- try_find_assigned_viewport("ED_A10C_CDU","CDU_SCREEN") try_find_assigned_viewport("ED_A10C_CMSC","CMSC_SCREEN") try_find_assigned_viewport("ED_A10C_CMSP","CMS_SCREEN") try_find_assigned_viewport("ED_A10C_CLOCK","CLOCK_SCREEN") And so on... Ideally, you should use OvGME or similar to do this as a Mod rather than manually editing the files each time there is an update.

I'm pretty sure that would be a NO, unless you use a third party solution such as IKARUS. See here:- https://forums.eagle.ru/showthread.php?t=179525&page=3

BUMP! It is nearly 2 years since this was first noted, and still nothing? Come on now guys.

Does anyone else have the problem that the Idle/Cuttoff portion of the Warthog throttle is being ignored? ATM, I can map the top end/AB detent as in above posts with a user curve, but no amount of fiddling will let me move the throttle below Idle. It is fine in other modules that use a throttle ide/cut-off, ie F-14.

It would be a lot simpler if they did the same as for the KA-50 Shkval and ABRIS, and just added a second name like this, so it works either way. If you add a Shkval entry, it uses that, otherwise it just uses the Left MFCD entry:- "try_find_assigned_viewport("Shkval","LEFT_MFCD")"