February 17, 20215 yr 1 hour ago, fmloyola said: Maybe who ajusted de signs is the same person who designed de trees height... and hangers.... 🤥 https://forums.flightsimulator.com/t/airport-hangers-height-issues-auto-generated/328619 CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB MOBO: ASUS Z170 Pro | GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K
February 17, 20215 yr 3 hours ago, abrams_tank said: Because the gateway scenery has been requested, which will allow the community to "crowd source" and fix the information on taxiway signs. I believe Asobo has looked into developing the gateway scenery, although I'm not sure when it will be completed. In any case, what's the point of the gateway scenery if the taxiway letters aren't big enough to read in the game? We can crowd source and fix all the information for every taxiway sign for every airport in MSFS. But all that is useless if we can't even read the taxiway signs (which we can now, because Asobo made the taxiway signs larger). Well I certainly hope there is a scenery gateway, as I have edited a dozen airports and would like to save others the hassle. But I haven't seen any confirmation that Asobo is intending to do that. But you are correct. It is nice, as I edit airports, to be able to use a bigger (but not these huge ones) sign. EddieKABQ
February 17, 20215 yr 41 minutes ago, haskell said: Well I certainly hope there is a scenery gateway, as I have edited a dozen airports and would like to save others the hassle. But I haven't seen any confirmation that Asobo is intending to do that. But you are correct. It is nice, as I edit airports, to be able to use a bigger (but not these huge ones) sign. You haven't seen any confirmation? They already (1) marked it as "in progress" in the feedback snapshot, (2) spoke about it extensively in an interview last week, and (3) brought it up several times in the Q&As. They even reached out to me last week for my input on the system as I emailed Jorg back a few months ago with my suggestions for how it could work. The scenery gateway system will be arriving in 2021, and it's actively being developed right now as one of the top priorities! https://twinfinite.net/2021/02/microsoft-flight-simulator-interview/ Edited February 17, 20215 yr by FlyingInACessna
February 17, 20215 yr 20 minutes ago, FlyingInACessna said: You haven't seen any confirmation? They already (1) marked it as "in progress" in the feedback snapshot, (2) spoke about it extensively in an interview last week, and (3) brought it up several times in the Q&As. They even reached out to me last week for my input on the system as I emailed Jorg back a few months ago with my suggestions for how it could work. The scenery gateway system will be arriving in 2021, and it's actively being developed right now as one of the top priorities. Awesome. Thanks for the link. Interesting read. I have over 100 airports on the "other sim" Gateway and would love to contribute to the growth of MSFS! Edited February 17, 20215 yr by haskell EddieKABQ
February 17, 20215 yr 5 hours ago, Mike S KPDX said: The oversize is pretty horrific. However what I find most interesting is why? I have searched the MSFS forum site (and AVSIM) and nowhere is this mentioned as an issue. So what prompted ASOBO to make this change? Personally I think this is a bug that was accidently triggered in the update. Especially with the now larger signs not being deconflicted with each other (i.e. physically intersecting signs due to oversize without relocation) It’s not caused by a bug. It is actually the correction of a previous bug in the scenery generation system, where the “size” parameter of a compiled taxiway sign object (which can be set from 1 to 5), was ignored, and all signs were rendered in-game at the smallest possible size (1), no matter what actual size had been specified. Apparently the signs that are now too large (or larger than they were before), had a size parameter larger than “1”. Scenery designers have been requesting this fix for quite some time. Edited February 17, 20215 yr by JRBarrett Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
February 17, 20215 yr Asobo should add a setting for those who prefer taxi signs small/medium/large. Each will regulate as they wish. In my opinion, i'm just saying that the taxi sign is too big.
February 18, 20215 yr I don't zoom in on them or park my Cessna next to them or get out my measuring tape and compare them against FAA regulations so I'm not as panic-stricken by them as some are. I can finally read them so I like it.
February 18, 20215 yr So the signs are more readable. But are they accurate? Last I checked taxiways were mostly randomly named. | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
February 18, 20215 yr Author It suddenly occurred to me tonight, as I was taxiing around my local muni, these new signs make the place look like a cemetery
February 18, 20215 yr 10 hours ago, desbean said: I don't zoom in on them or park my Cessna next to them or get out my measuring tape and compare them against FAA regulations so I'm not as panic-stricken by them as some are. I can finally read them so I like it. + 1 and for those i have seen so far, they are not to big. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base & hegykc MFG Crosswind modded pedals, TrackIR4, Rift-S for VR
February 18, 20215 yr 16 hours ago, JRBarrett said: It’s not caused by a bug. It is actually the correction of a previous bug in the scenery generation system, where the “size” parameter of a compiled taxiway sign object (which can be set from 1 to 5), was ignored, and all signs were rendered in-game at the smallest possible size (1), no matter what actual size had been specified. Apparently the signs that are now too large (or larger than they were before), had a size parameter larger than “1”. Scenery designers have been requesting this fix for quite some time. It’s still a bug though. Apparently the size parameters for non size-1 signs are massive and far larger than in real life. I’ve been attempting to get into contact with the devs & submitted a bug report with an Advisory Circular that has the real sizes.
February 18, 20215 yr 15 hours ago, desbean said: I don't zoom in on them or park my Cessna next to them or get out my measuring tape and compare them against FAA regulations so I'm not as panic-stricken by them as some are. I can finally read them so I like it. I’m glad the small size issue is fixed now, but you don’t need measuring tape to know that a taxiway sign is too large when it’s taller than the wings of a C172 😕
February 18, 20215 yr 15 hours ago, ryanbatcund said: So the signs are more readable. But are they accurate? Last I checked taxiways were mostly randomly named. Totally agree, too the folks here who state that these huge signs are 'required' while on VATSIM, if you are using the ingame signage as to lead you along correctly while on VATSIM - you are going to fail. You must use an airport map chart to correctly interact with VATSIM (and should have those anyways). CPU: Core i5-6600K 4 core (3.5GHz) - overclock to 4.3 | RAM: (1066 MHz) 16GB MOBO: ASUS Z170 Pro | GeForce GTX 1070 8GB | MONITOR: 2560 X 1440 2K
February 18, 20215 yr On 2/16/2021 at 7:32 PM, CaptainNick said: Yeah, they may be to big now, but at least I can read the darn things now.
Archived
This topic is now archived and is closed to further replies.