lwalter

I'm trying to understand what's happening with the INS update, whether by fly-over or by radar slant range. With both methods, I get the cross pointing to where the INS thinks the WPT is. Then I use either REC by fly-over or the "INS update" button in OBL/TAS mode with the diamond on the correct location. The offset is shown and I press "VAL". The L/G of the WPT doesn't change. I suppose this is normal as this should be real L/G of the WPT and only the INS internals itself is updated. However, the cross seems to stay where it was before update. I would expect the cross to move to the updated point. Am I missing something here?

Thanks! Any idea when they will be migrated? I like this idea of qualification missions for each plane or even combined arms vehicle. I don't mind buying them, as I did with the existing ones from Maple Flag, but I would almost expect ED to provide them as standard missions with their planes.

I have all the a10c training qualification campaigns + 1 of the F5 campaigns. I'm not done with all the missions, but so far I have enjoyed them. Today, I came across this website https://tlaschuk.github.io/missions There are many other "training" campaigns for the other DCS planes I have. However, they're not for sale on DCS Store or Steam. Are these campaigns/missions: - for older versions of DCS only? - downloadable for free but would need tweaking to make them work on the latest DCS vesion? - being rewritten?

That's good to know. Thanks for your explanation! So, it means that I would have been unable to land at Kutaisi using ILS, right? Is this considered to be a general issue with DCS? I'm wondering if there are plans to fix that when DCS team will work on the ATC improvements.

I could hear the outer and inner beacon tones. However, no morse code for the ILS station. Don't know if that's normal or not. The T-ILS page showed ILS ON.

I wanted to try an ILS landing on Kutaisi runway 26, ILS 109.75. I never got the f16 to get the localizer nor glideslope signal. The STRG CMD line above the ILS frequency on the DED never got highlighted either. Here are the all the steps I went through: - COM1 set to Kutaisi ATC 263.00 - called Kutaisi ATC for inbound. They gave me a heading to follow for 50, which I did. - I made sure ILS volume on Audio 2 panel was not OFF - on T-ILS page, I entered 109.75 as the ILS frequency and 254 for the course - on the HSI, I set course to 254 and chose PLS-NAV mode (also tried PLS-TCN but didn't work either) - When crossing Kutaisi landing course, I was at less than 5000 ft altitude and still no ILS signal caught... - Finally Kutaisi ATC contacted me "clearly for visual" and switched on the airport lights. At least I could do a "visual landing". ILS completely let me down on this one. I"m probably doing something wrong or missing a step, but I read the F16 DCS manual twice for the ILS section and couldn't find it. Any help here would be appreciated.

Thanks JasonJ! I tried comparing visibility range low and visibility range extreme, when trees visibility is at lowest (30%) Whether in low or extreme, I get these "2D trees". The only difference in extreme is that when I get closer to them, they transform into "3D trees". It doesn't do that in visibility low or really when you almost touching the tree. ----However, when I put tree visibility to 100%, in visibility range extreme, I seem to have no more "2D trees". With visibility range low, even with 100% tree visibility, still "2D trees". ----I may now have to find a sweet spot for both these settings. EDIT: Actually, even with visibility range extreme and 100% tree visibility, I can see the "2D trees". It's just that they're further away and they change to 3D trees from further away than when in visibility range low, but they're still too easy to spot :(

I can't argue whether these "2D trees" already existed before 2.5.6 or not. Maybe I never noticed them before, but for sure I noticed them since early of June without changing any graphic settings. If I'd like to see "3D tress" instead, which setting or settings should I update? Here are my main current settings: - Textures: high for both - Visib range: low - Shadows: flat only - clutter/grass: 1000 - tree visib: 80%

I'm using the latest open beta. Until the last 2 or 3 open beta updates, the trees in Caucasus were all really nicely rendered. Lately, I have noticed that there are now these ugly and simplistic 2D-like trees appearing. It seems to be only 1 sort of trees as all the other ones still look nice. Is it something others have noticed lately? Note that I haven't changed settings or hardware. I attached a screenshot. Granted the screenshot doesn't look as nice as in-game (I don't know why) but you can definitely see the "2D" trees.

The blueish instrument lighting was ok for me. Actually, I initally thought that it looked nice this way :) However, what quite disturbing to me currently is that it's impossible to read the lighting for the afterburner stages or the autopilot ones. Are you also working on fixing those?

As soon as this map got available, I bought it and flew for a few hours over the French coast and inland to get some impression. I read several posts mentioning that it was an awesome map. My personal opinion is more mixed, especially as I tend to compare it to the other maps I have: Caucasus, NTTR, Persian Gulf and Normandy. This is my personal first impression and it doesn't reflect what others may think of this map. It may also change after more flying across this map. First, the really good aspects: - the countryside, the cliffs, the beaches - the overall layout of the harbors. For example, I immediately recognized Fécamp harbor, which I visited a few years ago - seeing the Dover cliffs while flying over the French coast is just so well done - the landmark buildings (although too few in my opinion) The not so good: It looks a lot like the Normandy map. No, i was not expecting desert or canyons... I mean I was expecting it to be better visually, more detailed, etc... To my eyes, there's not that much difference. Countryside is countryside, but the towns are the real let down for me. I'm not expecting each and every house to be modelled, but at least the main buildings of each town: typical churches, town halls, main squares, etc... As of now, except for a very few famous landmarks, all towns seems like just a bunch of random houses. When looking at Persian Gulf (and some picture of future Syria map), it's definitely not as good. Maybe my graphic settings are not high enough to fully enjoy this map. Textures and terrain textures are High, water is High, visib range is low, clutter/grass is 1000, tree visibility 80%. Other maps like PG look already great with these settings. Would increasing visib range and clutter grass change my perception of this map?

Same here: can't see the "steering wheel" light at any time of the day, since latest open beta. Before that, it was clearly visible. It doesn't seem to be only an a10c issue. Today, I was flying the ASJ37 and the afterburner lights were impossible to tell whhether there were on or not. Is there already a bug on this one? I haven't found any when I did a search.

My gamma is 1.9

Maybe I haven't noticed it before, but with the latest beta (June 5-6), even if I pull all the inside lights (console, instruments, etc...) to the max, there's still barely enough light to read anything... Only MFCDs, HUD and engine gauges are bright enough and readable. More, the flashlight doesn't seem to work or to be bright enough.

When I activate the jammer with "CMS push", the jammer starts operating. However, it lasts only for a little while. Is this the normal behavior? I thought it was more like a toggle switch: push once => activate jammer, push once again => deactivate jammer.

I'll be happy too when this is fixed, and the earlier the better! In normal play, you have to move your head around to see everything from the HUD display. It's a pain but still bearable. However, when you want to change options in the IFFCC, it's impossible because the top lines are truncated... for example, I'm currently unable to change the consent release options.

same here posted the same issue under the a10c/crash section

Same here with latest open beta I don't know the exact root cause, but it's linked to missile launches and missile warning system, one freeze I got when there was a SA8 launch, another freeze when a friendly F16 was launching a missile against a SU25. This happened yesterday and today again on mission 2 of Georgian Hammer campaign

I saw 2 other posts in this forum but they don't help: - in the first thread, one says there's a bug, while others claim it works - in the second thread, I read that you should be able to ask for "landing clearance", but I don't get this in my available radio messages This is what I'm doing: - time is about midnight, so completely dark - TACAN and ILCS properly tuned in and bringing me to the carrier - radio call for inbound works - the carrier has some lights on, but impossible to actually tell the landing zone from the rest Then, I get very close to the carrier and nothing else happens: - not possible to call for landing clearance - no lights switching on What's the right procedure to get it to work? or is it really a bug? (I'm currently with the latest beta)

I think you got it. I usually do stored alignment and this time I went through full alignment and didn't confirm the coordinates... Thanks Svend and Deano! I have a side question: how come the HSD would still work properly?

Do you have anything special to do to confirm your position? The default coordinates were fine.

Yesterday, I played one of the missions coming with the F16, where you have to bomb anti-ship missiles located on an island of the Persian Gulf. I went through normal INS alignement and waited until "ALIGN" flashed on the HUD, before moving the INS switch to "NAV". The HSD was displaying the waypoints properly. The DED was showing the waypoint with correct long/lat and elevation. However in the HUD, the diamond supposed to show the waypoint was always stuck in the middle. The distance and time info to waypoint in the bottom right of the HUD where always stuck to 000, except the waypoint number. Has it every happening to anybody else? Or does it ring a bell to somebody about something wrong I may have done? I have a track file, but it's over 30 MB large. I don't know if I can upload it here.

I don't know if this is going to help much, but I noticed that when changing the time of my mission to morning, evening or night (instead of the default noon), then the flickering never happens in several hours of play or very rarely (only once yesterday).

Here's a very short track. As I explained above in the thread, when replaying this track, it doesn't necessarily show the flickering. The other way round, any track plays with the flickering when DCS enters this "flickering mode". flickering.trk

Checked all of that and deleted metashader2 and fxo folders, but flickering still gets back after about 8 mission starts from Mission Editor :( I'll check whether this is happening only when starting from mission editor or also from other parts of DCS (instant action, campaign, etc...)