twharrell

It seems Bill already does a good job modelling 3D gauges for MilViz as the Mindstar G1000 and GNS units fit near perfectly in the 310. Some size adjusting is needed but he isn't far off the mark. Once the adjustments are made, MilViz will be well ahead of everyone else as far as Mindstar integration is concerned. I don't think Mindstar has any interest in getting into the VC modelling business as they have more important and lucritive things on their plate to fry. I, of course, don't speak for Ed or Stasi. I have been known to be wrong before...... Todd

FYI, for those wanting to use either the GNS430 or 530 in the A2A C172: create a new blank text file on your desktop and rename it 'rxpGNS.dll'. Place this dummy file into your FSX or P3D/Gauges folder or else modifying the panel.cfg file alone won't work. The A2A C172 has to think you have RXP installed for it to give you those panel options. It's a crude workaround that works well. And a thank you to the person that helped me figure this out during beta testing. Todd

Turning tesselation OFF fixed my bouncing issues.

Ronzie, that is interesting because here is what my RC4 window looks like after selecting the flight plan: Here's some additional info: I am using P3Dv2. I moved both of my RC4 folders over from P3Dv1.4, placed the newest copy of makerunways in my P3Dv2 root folder, rebuilt the database, and now having this issue. Is there something else I need to make it work in P3Dv2? Todd

I was wondering if anyone has successfully imported and used a flight plan file created with SimBrief. I tried the other day with no luck. I am placing a copy of that file here in hopes a solution might be reached as to why it won't work. This is a FSX flight plan file from KPHL to KIAD created with Simbrief (route is MXE HYPER4). Thanks, Todd <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>KPHL to KIAD</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>14000</CruisingAlt> <DepartureID>KPHL</DepartureID> <DepartureLLA>N39° 52' 20.10",W075° 14' 27.12",+000036.00</DepartureLLA> <DestinationID>KIAD</DestinationID> <DestinationLLA>N38° 56' 50.80",W077° 27' 35.80",+000313.00</DestinationLLA> <Descr>KPHL to KIAD created by SimBrief</Descr> <DeparturePosition>27L</DeparturePosition> <DepartureName>PHILADELPHIA INTL</DepartureName> <DestinationName>WASHINGTON DULLES INTL</DestinationName> <AppVersion> <AppVersionMajor>10</AppVersionMajor> <AppVersionBuild>61472</AppVersionBuild> </AppVersion> <ATCWaypoint id="KPHL"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N39° 52' 20.10",W075° 14' 27.12",+000036.00</WorldPosition> <ICAO> <ICAOIdent>KPHL</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MXE"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N39° 55' 05.00",W075° 40' 14.91",+000000.00</WorldPosition> <ICAO> <ICAOIdent>MXE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="DELRO"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 57' 55.71",W076° 37' 31.24",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>DELRO</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="BINNS"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 47' 06.22",W077° 00' 39.58",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>BINNS</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="HYPER"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 41' 02.16",W077° 13' 30.34",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>HYPER</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MULRR"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 37' 53.12",W077° 20' 08.51",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>MULRR</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="SIGBE"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 24' 37.20",W077° 21' 49.20",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>SIGBE</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="MOWAT"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 15' 57.60",W077° 21' 36.60",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>MOWAT</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="HUSEL"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N39° 09' 51.60",W077° 21' 27.60",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>HUSEL</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="YACKK"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N38° 54' 28.80",W077° 21' 25.20",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>YACKK</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="TICON"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>N38° 40' 45.60",W077° 21' 42.60",+000000.00</WorldPosition> <ATCAirway>HYPER4</ATCAirway> <ICAO> <ICAOIdent>TICON</ICAOIdent> </ICAO> </ATCWaypoint> <ATCWaypoint id="KIAD"> <ATCWaypointType>Airport</ATCWaypointType> <WorldPosition>N38° 56' 50.80",W077° 27' 35.80",+000313.00</WorldPosition> <ICAO> <ICAOIdent>KIAD</ICAOIdent> </ICAO> </ATCWaypoint> </FlightPlan.FlightPlan> </SimBase.Document>

If you are a fan of props, go get this one. One of my favorite aircraft so far. Todd

My apologies if this is "old" information, but if you migrate to your Lockheed Martin folder from the Start menu, open the Training Center and there is a whole section of suggested tweaks for the P3D.cfg file published by LM. Affinity Mask=14 is one of the suggested tweaks. Todd

Bump.

Even that only helps a little. AA is definitely a weak point with P3Dv2. Todd

I don't have this issue or the CDT at all in P3Dv2 (I did in v1.4), but I do have bouncing issues with other aircraft (RealAir Turbine Duke, for example). Apparently LM is aware of the problem and is working on a fix in their next patch. As for the Q400 specifically, the Majestic folks have stated that you can't have the Q400 installed on 2 separate hard drives. So if you plan to install in both FSX and P3D, ideally both should be on the same drive. You can read more about it on the Majestic forums. Todd

Yes, it works. Just point the installer to your Prepar3D folder, then make sure you put Tongass X below all Orbx/FTX entries in the scenery library. Todd

Is anyone else experiencing AI aircraft with no nav, strobe, or landing lights? I have WoAI installed in P3Dv2 as well as PilotEdge. In both cases, alll AI aircraft lack nav, strobe, and landing lights. I have yet to get an answer anywhere about this issue (granted, P3Dv2 is still young, so I don't expect miracles), so I was hoping to at least know this isn't an isolated issue. Hopefully there will be fix suggested or perhaps released with the first patch. Todd

Nice repaints, Ron. I love the MilViz C310. Todd

I just pointed the installer to my Prepare3D v2 folder and it worked. No utilities needed on my end. The only major issue I am having is intermittent bouncing during taxi and takeoff. Once airborne, it is smooth. Anyone else experiencing this? Todd

Is anyone else experiencing an issue with bouncing while taxiing using the Turbine Duke? I have that problem. Otherwise, it works great once I am airborne. Todd

I have a feeling the MilViz KA350 is several months away from release. It looks to be a pretty complex bird. You can go to their forums to see the completed external model and cockpit shots. All of Mindstar's products are and will be compatible with P3Dv2. The release of the GNS 530/430 package was delayed for a variety of reasons, but it will be out this year. Compatibility depends on the aircraft developer, nor Mindstar. We, the customer have to demand compatibility from the likes of Carenado, etc. I will say not to hold your breath over any Carenado product being compatible, as Carenado has told me several times they are not interested. Shame. If they would allow Mindstar G1000 integration I think they would almost double their customer base. I'd buy the 182T and 206 in a heartbeat if I could add the Mindstar G1000. As for the Phenom, adding the G1000 isn't so cut and dry as the Phenom uses a custom Garmin G1000 suite that would essentially require a new gauge from Mindstar. Unless there is commercial demand for that, it just won't happen. Todd

You need to check out the MilViz King Air 350 in development.

+1. But I doubt it will happen. I asked them about being able to do so in the C182T and they replied that they have zero interest. All looks, but zero brain. That's Carenado for you.

Any more reports on the TBM? I'm very curious about the G1000 functionality. Can Navdata be updated using Navigraph or NavdataPro? Todd

God bless you and your family, John. Your priorities are where they need to be, and that is a good lesson for us all. Thank you for your huge contribution to the flight simulation community. Todd

With all due repect to you, why don't you just buy one subscription and then choose to never update the product again? Even then, you'll have spent only $90 for 2 gauges, crossfill, and a complete nav database that you can use indefinitely and get free upgrades to gauge functionality, like WAAS. That's still a bargain. And I also don't understand what you don't understand about Ed's repeated statements that they cannot legally include a Navdata cycle with the gauges. Todd

I really feel for developers who depend on the flight sim community for the success of their products, not to mention their income in some cases. It's no wonder developers are closing shop almost weekly.

Who has been misleading, JetFueler? Exactly what "misleading statements" are you referring to? Questions are, and have been, welcomed and encouraged. I think both Ed and myself have been very forthright. Todd

Meanwhile.... A2A Cessna 172 with Mindstar GNS 530: A2A Cessna 172 with Mindstar GNS 430: Todd

Ed, you used my last name! Now my cover is really blown! ; b