Akila

Yes, it is fixed. thanks!!!!

Nice one. for me all my folders are mixed case (uppercase and lower case). I believe many people use mixed case in the folder structure / names (my assumption). Example: Another Example:

Hi @Bad_T , I am sending you all the AddonLinker data (ProgramData/Presets - Total size: 800k), that way I assume you can reproduce the error. https://www.mediafire.com/folder/p2tzv7vbwhhb2/AddonLinker BTW - pressing F8 or via the menu has no difference. NOTE: it might be related. the presets & Addons_SymbolicLinks.bin, were all migrated from 2020. it might be related to the issue.

When pressing the F8 on any addon I try, it will always show that it doesn't belong to any preset even though it does (MSFS_AddonsLinker_2024.exe) . I tried many addons that are in one or more preset(s). If i select / apply the preset it does populate my community folder with the Symbolic links, but on the preset assignment (F8) it doesn't reflect that those are part of any preset(s). Also CTRL+M (preset manager), I do see all my addons in the correct presets, so they are for sure in those presets.

Would it work well on an older GPU (GTX 1080 Ti) or you need an RTX based card?

So is it now in what's called the "Tech" (pre Beta) pashe?

No, it is not related rather the monitor is calibrated or not or I would see some difference between values in the settings (e.g. NIGHT_THRESHOLD=0 vs. NIGHT_THRESHOLD=4096), it has no effect at all. also I use the same Monitor (two monitors) today with P3Dv3 I used with FSX and P3D v2.5 and the same OS. so calibration for sure did not change and as I said in my original post, it used to work on the previous versions. also as I mentioned, I don't use HDR and my P3D is a fresh Install from few days ago. did not manage to add any addons yet, so my CFG file is the default one. it is not a monitor issue nor .CFG, it is the P3D software that decided to add more light at night. it has nothing to do with the hardware.. I am searching for the NIGHT_THRESHOLD substitute that used to work up until P3Dv2.5 (not sure about P3Dv3.0 / 3.1 - never had those, I jumped Directly to v3.2)

anyone? anything?

In the Simulator the night exposure is way to bright, which allows you to perform a VFR flight at night without the needs of the artificial horizon gauge even when you fly over the water (sea) or at dark places such as forests or a desert.... In reality, when flying over the city at night in VFR, all you only see is the street lights and maybe car's headlights on the road or anything that emits light. It is impossible (in the best case scenario) to see the external horizon line and in worse case scenario, mistaking the street lights line as the external horizon line (very dangerous),you for sure do not see the ground/terrain, hence there is a the need to use the artificial horizon gauge also on VFR flights at night. there used to be an old school tweak which you could put in the line in the CFG file that would correct this a bit and got you closer to reality vision at night (still wasn't perfect). [GRAPHICS] NIGHT_THRESHOLD=0 for some reason this no longer works or has any effect on P3Dv3. Also the following settings based on the SDK documentation, doesn't have any effect either. [GRAPHICS] TONEMAP_NIGHT_EXPOSURE_KEY=0.000000 Do you know what is the equivalent settings in P3Dv3 for NIGHT_THRESHOLD=0? I don't use HDR settings and even if I would I believe playing around with the HDR settings would effect the amount of brightness/darkness during the day as well which I do not wish to touch or change.

can someone please post a full description of the issue? reading through all those posts in this thread I couldn't figure out exactly what the problem is, only what products "a problem" potentially exists. Picture or a Video would be helpful ...

nice!!!! keep it up

You got some inaccuracies in your assumptions I'll try and start 1. not every Runway has a SID/STAR even though they are both used for IFR. here is one. VTBS in Bangkok 01L / 01R , both are used only for commercial flights but yet one of them has a STAR while the other doesn't and vice versa , one has a STAR while the other is R/V based. same with OTHH, Hamad Intl airport in Qatar. take an example RWY 16L/R departure to MUXOP, 16R has a SID while 16L doesn't, but both are for IFR flights only. I can give you tons of examples... Why this fact is important? because the claim that VoxATC can be "smart" and give you the right runway if you are a VFR or IFR based on the existence of SID is invalid, it can't as there is no World wide standard. 2. regarding AI, Vox doesn't change the AI behavior, it only spawns it for you, but FSX is still the AI engine that drives it. but that is not relevant either. how would Vox handle the active runway better as you say, if it doesn't know what is the active runway? the only way it could know is based on AFCAD.... vox also doesn't have a way to know which one is for VFR and which one is for IFR, it can guess, but then Vox will miss other stuff at other airports that don't follow this logic and you'll get complains here the the way around. In other words what you are asking for, is for VoxATC to search & discover NOTAMS around the world and practice them. bottom line Vox can't manage the runways better as they don't have the info of each airport and runway in use and not in use of each and every airport in the world, nor do they have the info of best practices based on countries, etc. never the less not to mention keeping track with changes. we are back to AFCAD then :wink:

probably, but so far I am pretty happy with my P3Dv2.5, so it's not such a big issue for me to wait a bit longer just the thought of having to reconfigure everything from scratch and installing everything gives me the shivers, never the less doing it twice if I would had decided to migrate now to P3Dv3.

Wait for P3D v3.2 before you migrate.... under my experience on many heavy coded products such as Simulators, OS, etc., usually only after the 2nd Support Pack of a Major release you get to some kind of stability. the same was true with P3Dv2. only when 2.2 was released (some would even say only when v2.3), you got a satisfied product stability. that is what I am planing on doing. I am waiting for v3.2

when I say problem with an AFCAD I don't mean there is an actual problem in the AFCAD. it means it doesn't contains the information needed for Vox to do it's job. and yes, Aerosoft and Flytampa in many cases don't include this information that Vox needs in the AFCAD. it is not the 1st time I had to fix their AFCADs to contain some missing information. However it is not only Aerosoft/flytampa to blame. it is also the FSX/P3D engine on how it works and the ability and limitations on what you can reflect in the AFCAD. there is no way to set int the AFCAD what RWY to use based on flight type, such as VFR/IFR. you can't expect Vox to try and guess what RWY to assign you if no one can provide this information to the Vox engine. in the AFCAD it states that both RWYs are in use for T/O, Vox will pick them randomly as there is no other governance to provide a guide line when to use what. and for sure I don't expect Vox to know each and every Airport what is the best practices of what RWY to use. it must base it on the AFCAD and that is the AFCAD limitations, not Vox.

it is not Voxt faults, it is an AFCAD issue. the AFCAD was set improperly, all VOX does is reading the AFCAD

so why you selected "nam1394" as the one that answered it? :smile: (best answer)

Although @spesimen is right in his reply , I believe it added more confusion to what you already have and not totally answered your questions. 1. that is correct you don't normally file a SID/STAR as part of the flight plan, although VOXAtc supports those if you do decide to file. In general SID/STAR are based on the RWY in use and the air route which you came from. 2. as to your "complicated" question on how to set your plan to include the waypoint which in return trigger a SID/STAR? don't sweat over it. file a flight plan from the Airport, up until the airport (usually the airport VORs), 99% of the times the SID/STAR waypoint will be in it already, under the assumption there is a SID/STAR for that airway. VOX doesn't needs the waypoint to be at the beginning/end of the flight plan to assign you a SID/STAR. it just needs to contain it. 99% of the flight plans you will download from all kind of FP tools and websites, such as vroute, etc., contain the SID/STAR waypoint in them already.

do you know by any chance if the same (issue) is true in P3D v2.5 / 3.x?

bumpty bumpty, bump

I have tried it before the EGLL-KJFK format and it yield nothing. ​do they have a support forum or an email or something you can approach them?

One very nice feature that I often used on Vataware's is the Top Routes. These are the most flown routes for a city pair and therefore "tend to be" a nice route suggestion. I use it mainly on weird routes that don't appear in regular route DBs on the net.. however since the new Vataware site I can't seem to find a way to search for the Top 10 or any city pair search. do you guys know by any chance how to run a "city pair / top 10 routes" search in vataware these days?

out of all this RNAV (GNSS) with LNAV only (not LNAV/VNAV) on a chart (ICAO Airports/charts - outside the US) is considured RNP or not?

could you address me to the afformentioned post about the v3, v4 roadmap?

nice stuff!!!!