docromano

I´m having a graphical issue. With HDR on, when flying in rain, it looks strange. Additionally, there are no light visible at the runway when using wipers. If I use an exterior view, everything is fine. There must be something with the rain code that doesn´t work with the new hdr rendering

@Kyle Thx for that Information! @Japo Hmmmm...that´s sad. I will continue to hope for the best and see full XSB functionality in the CRJ. I assume that more than half of all CRJ Pilots do VATSIM flights and they´d probably share my joy about this feature

I did a few few online flights with some freeware jets, for example the stock 747 that comes with xp10 and an A346. Again, TCAS and weather work very well in those planes, getting their data from XSB. For some reason this data does not make it into the CRJ PFDs. As it is possible to display it in other planes, why not in the CRJ ? It would be really great if you could have a look into this as it makes flying online a lot more realistic and easier.

Could you give us some details concerning the "missing fixes in the Windows version" ? thx!

When accelerating, the nice raindrops turn to "running" water. However, the "static" raindrops persist in parallel. I believe I didnt see this in an earlier version. Any way to remove static drops when moving faster ?

This Works with other Planes in XP very well - wxr and tcas in combination with xsb. In the Crj it doesnt, which is wgy I assumed a Problem here.

Just wanted to create a short film of my beautiful CRJ and noticed, that it has a flying GPU This only happens in replay mode.

I don´t know if this is something for xsquawkbox support or this forum - I guess you will tell me Being a VA pilot, xsquawkbox is active on every flight. The interaction with xp10 works quite well, xsb weather is displayed on the panels and other planes show up there, too. Both are not visible in the crj. Especially other planes would be nice to see to be able to avoid mid-air collisions on busy days. It´s not THAT important, but would be a nice feature to develop/integrate, since it is working fine on all other planes.

I´ve seen this on several departures now, but not on all. Route: LICA-LFMN BAGIX UQ182 NERAR UM601 RONAB UL12 ELB UM616 AKUTI R16 KERIT Departing rwy 28, SID BAGI5E After takeoff, suddenly a new waypoint is inserted (see attached file). This waypoint is obviously wrong and has to be deleted. It was not inserted when activating the SID, but after takeoff without any user interaction.

I solved this as posted above - new driver (wanted to get that anyway) from a 285 to a 295, clean re-install. Also I opened the plane, closed Xplane and started it again as recommended in one of the other threads. Works now.

I did a clean re-install and did not check any livery because I have a custom one from my VA. Nevertheless, all available liveries were installed. Version 1.4.3

Thanks ! Sadly, as with the last update, the PFD stays black issue has returned :/ What should I do ? NVIDIA driver beta update, clean install ?

Oops ! LFLSLZTT.zip

No problem Go to LFLS, rwy 27, load the flightplan. Then insert the SID SOPLO2H. Then go to the DCT page and click NAVLA.

Hi Cameron, sorry saw that too late (I´m too busy with the CTD when DCT issue). The new NVIDIA driver 295.51 resolved the PFD black problem.

I tried it with the new AIRAC 1201, vasfmc native data. Removed the contents of navdata folder and put the new data in. Same CTD.

...and again, with no plugins at all. I think I have to go back to VasFMC for this flight :/

Ok, now I got something reproducible. I go to LFLS, rwy 27. Then I load the flightplan as posted above. Then I insert the SID SOPLO2H. Then I go to the DCT page and click NAVLA. Just pushing the button beneath NAVLA results in the immediate CTD. I will try again with NO plugins.

I know that. The thing is that this CTD comes randomly and I don´t have the time for flying hours with the demo just to see if a DCT leads to a crash. Just had another crash after a DCT to one of the first waypoints (keeping in mind what Phillip said). I removed everything but saitek panels, XSB and pushback and XACARS now. Testing again.

Javier, the frameworks stuff belongs to XP10 as it seems. If I remove them, I get a message they are missing and XP refuses to start. Removing Xacars and XSB is pointless for me but maybe I will try it out later. For now I´m downloading the current NVIDIA driver (see PFD black topic) and did a clean re-install. I´ll report back .

Same here after a complete re-install including deletion of all old CRJ Folders. PFDs staying black, CDU working. Before the re-install it worked good, even after the updates. Driver 290.53. Trying the recent beta now.

Sure thing ! The navdata Folder is empty, seems to be a remain of an older version.

...and again. This is starting to suck a little I was enroute the same route posted above. Shortly before ABLOM I got the direct to EPEDA. I didn´t want to use the DCT function so I did what usually works. Enter the waypoint and click on the current one to get it exchanged with the new one. Worked a few minutes earlier with another direct from controller. This time - CTD. After almost 90min of flight for my VA which was ended by a CTD for the third time. I`m thinking of going back to vasFMC because at the moment it´s really "dangerous" to fly a longer route online since there are controllers and modifications to the route... For now its only a feeling but I think I had less CTDs with the last version 1.4.1.

I just had another CTD using 1.4.2 Route was LFLS SOPLO N871 OMASI UQ224 GAMSA UN871 BADVI UL725 LEDRI UM985 NIT A42 SLC R53 EPEDA LZTT Shortly after GAMSA the controller gave me DCT XEBIX at FL330. I pushed the DCT button, then XEBIX and doing that I got the CTD. Again, no crash log, just cycle dump and log. Navdata not changed or updated, just raw CRJ-1.4.2 Since all my CTDs were associated with DCTs I will stop using that function for now.

FMS Bug: Enroute LIPX-LFLS after enabling a STAR and performing a DCT to a point within it, CTD. A crash_log was not created, Ill attach the log.txt /edit Again CTD when performing DCT. Im using AIRAC 1201 vasFMC native, copied as recommended. I will do a re-install and keep the included navdata...maybe that helps. Log.rar