Hans Hartmann
-
Posts
5161 -
Joined
-
Last visited
-
Days Won
37
Content Type
Profiles
Forums
Downloads
Posts posted by Hans Hartmann
-
-
4 hours ago, ahmed2003 said:
Really, you will develop a detailed cabin in your CRJ!! that's very cool and what about the a330 would you do so?
I'm not a modeller, just a programmer. Somebody else is designing the CRJ cabins. I don't know what the plans for the A330 are.
-
1
-
2
-
-
- Popular Post
- Popular Post
It's simple: While you are asking me to give you more information, other developers get hell from their community because they can't keep announced release dates (for whatever reason. I'm not judging them because I know the work that is involved. If it takes longer, it takes longer. It won't kill anyone). I don't want this. Just look at what happens in the Fenix Discord right now (after they announced the delay of their Block 2 update) and you will understand why I'm going with "It's done when it's done". I'm not a friend of creating hypes or posting WIP screenshots every other day. Expect to see screenshots and more detailed feature information when we're well into beta testing.
I promise you that there will be a CRJ update, although it will likely not be released before the end of the year, that it will be a major one, that it will include the much awaited LNAV/VNAV fixes as well as Simbrief, Navigraph Charts, an updated model with a detailed cabin and more.
-
15
-
3
-
7
-
- Popular Post
- Popular Post
18 hours ago, Brand0n said:I'll do the honors for the eulogy...
Here lies the first highER fidelity addon in MSFS. Though it was beloved by so many, it's parents didn't give the same love to it as they have shown it's other more lucrative siblings. Though its parents didn't treat it as badly as it's brother (the Twotter), it still did long for its parents' love and affection. It lived a short life but brought joy to so many for an extended period of time, but it's flaws were too great to continue to go unnoticed when compared to its competition. Only its parents held the power to fix its flaws but alas, here we are. Thank you CRJ, you will be missed.
Thanks for the eulogy. I guess, since apparently know more about the CRJ project than me, I can stop working now.
So, here's the deal: There is a major update in the works (free, of course). It will involve fixes to the LNAV and VNAV issues and stuff like Simbrief integration. There will be quite a few additional features, but these will not be published at this point. Same goes for a release date. There is none. The update will be released when we (PM, myself and the testing team) think that it's ready for release.
Staff changes at Aerosoft do not affect the work on the CRJ in any way.
This is all for now.
-
2
-
3
-
10
-
8 minutes ago, The Dude said:
I would say that if you can make a MSFS A333 you can also make an A350 that is somewhat believable. All this talk about ultra realism is partly just PR. There are enough A350 FCOMs floating around on the net. There are also enough videos and pictures to be found. Then you have some pilots that are willing to assist.
The A350, IRL, can also be flown when having an A330 Typerating and doing just a few simulator missions as a RW Pilot. The A350 flight characteristics are closly matched to the A330 because of this.
MSFS add ons do not need to model different internal A350 Network environments, systems and such. If you are just doing normal SOPs you could get a pretty good A350 if you took the A330 code as a baseline. Engine wise there is also not that much of a difference to the Trents except for fuel flow and small parameters that a sim pilot would not notice at all when comparing the two.
I can see that the Airport Navigation Function and BTV would be the biggest differences with the A333 and maybe AS could just switch them inop for the initial release.
Hoping for that A350 in MSFS….
A clear no, just because you want it
-
1
-
5
-
-
No sorry, there are no L or A variables for the standby frequencies in the instruments themselves. Because the frequencies need to be synchronized between three different instruments (MCDU, RTU, BTU), everything is handled internally in C++ variables
-
Wenn Du in der EFB auf der OPTIONS-Seite unten auf "Show Clickspot Help" klickst, dann kriegst du eine Grafik, die zeigt, wo welche Clickspots sind. Dass die Fenster vom Sim aufgehen, ist allerdings so nicht geplant. Bei mir hier passiert das allerdings auch nicht.
-
AVX, wie in dem Thread erwähnt, wäre vielleicht eine Möglichkeit. @AC2436, was hast Du für eine CPU in Deinem Rechner?
-
27 minutes ago, AC2436 said:
ATR gekauft Cockpitdisplays bleiben dunkel Tablett auch keine function mehrfach deinstalliert kein Erfolg.
Sehr geehrter Herr Hartmann bitte um Hilfe weil von Microsoft Hilfe zu erwarten bleibt wohl Hoffnungslos
Meine Mail : <removed by moderator>
MIT F.G. AC2436
Hallo,
leider habe ich keine Idee, was das sein könnte. Bisher ist mir nichts in der Richtung untergekommen. Es gibt auch keine besonderen Voraussetzungen, außer für die Xbox, wo man wohl dieses Add-on Support DLC benötigt, was aber meines Wissens automatisch mit installiert wird. Am Ende kann wohl tatsächlich der Microsoft Support am ehesten helfen - zumindest wenn die das Problem schon mal gesehen haben.
-
16 hours ago, Agrajag27 said:
Thanks! This is perfect. It'd be great if a future verion of the CRJ added a couple of these for the sake of the Bravo and other cockpit builders.
Yes, now that the stressful release phase for the ATR is over, I plan to start working on a major update for the CRJ. No release date yet, we want to do this properly.
-
2
-
1
-
3
-
-
On 4/16/2023 at 7:30 PM, Agrajag27 said:
Guys, nearly done getting everything just right with my Alpha and Bravo and the CRJ, but have a few last pieces to put in place and hoped you could help. Some of the Bravo LEDs may not apply for the CRJ, but I wasn't sure. I also wonder if the manuals include all the data I need for what I'm looking for (like all the numbers when when a warning trips for these items). This isn't really meant as a support post, but a community assist post assuming someone else has already tackled this.
This all relates to the Bravo LED panel and getting it somewhat right with the CRJ. Any help with any of these would be greatly appreciated.
- Is there an easy way to trigger an engine fire to make sure I've got that working right?
There's no engine fire simulation in the CRJ itself. All you can do so far is to trigger the FS failure. However, I never tried if that does anything.
- Does the Vacuum light serve any purpose in a CRJ? I set a sim var to the generic "(A:WARNING VACUUM, Bool)" and that seems to work. It comes on after hitting the master battery and goes off after a period, but I'm not sure it's valid or specifically when it should go on and off.
Vaccum is not relevant for a jet. It's something that pistons and may be small turboprops use.
- Starter Engaged. I just have it set to "(A:GENERAL ENG STARTER ACTIVE,Bool)", but it never fires off after I push the Start button on each engine.
You need to use (A:GENERAL ENGINE STARTER ACTIVE:1,bool) (A:GENERAL ENGINE STARTER ACTIVE:2, bool) || for this
- Low Voltage. Set this to "(A:ELECTRICAL MAIN BUS VOLTAGE, volts) 24.5 <=" but I just guessed as to the right voltage. Any idea what the correct one is for the CRJ?
MSFS' electrical system is not used in the CRJ except for the batteries and generators. Everything else is custom made. No Lvars are currently available for it.
- Low Fuel Pressure. Set it as followed. Are the settings right? (A:GENERAL ENG FUEL PRESSURE:1, psi) 10 <= (A:GENERAL ENG FUEL PRESSURE:2, psi) 10 <= ||
Same for the hydraulic system. It doesn't use any of the A: vars. Everything is done internally.
- LOW HYD PRESSURE. Assuming it's like low oil, but what would this look like?
No, sorry. This isn't used either.
- Anti-Ice. Not sure when this should light or exactly what it should look at. Is it lit when I haven't flipped on the LH and RH Windshield switches as that seems to match the error on the PFD.
(A:STRUCTURAL DEICE SWITCH, bool), (A:ENG ANTI ICE:1, bool), (A:ENG ANTI ICE:2,bool) and (A:WINDSHIELD DEICE SWITCH, bool) might help you there. Either use just one or OR them all together.
Thanks!
I edited the answer into the text above. I hope it helps at least a bit.
-
1
-
1
-
-
On 4/16/2023 at 7:30 PM, Agrajag27 said:
Guys, nearly done getting everything just right with my Alpha and Bravo and the CRJ, but have a few last pieces to put in place and hoped you could help. Some of the Bravo LEDs may not apply for the CRJ, but I wasn't sure. I also wonder if the manuals include all the data I need for what I'm looking for (like all the numbers when when a warning trips for these items). This isn't really meant as a support post, but a community assist post assuming someone else has already tackled this.
This all relates to the Bravo LED panel and getting it somewhat right with the CRJ. Any help with any of these would be greatly appreciated.
- Is there an easy way to trigger an engine fire to make sure I've got that working right?
- Does the Vacuum light serve any purpose in a CRJ? I set a sim var to the generic "(A:WARNING VACUUM, Bool)" and that seems to work. It comes on after hitting the master battery and goes off after a period, but I'm not sure it's valid or specifically when it should go on and off.
- Starter Engaged. I just have it set to "(A:GENERAL ENG STARTER ACTIVE,Bool)", but it never fires off after I push the Start button on each engine.
- Low Voltage. Set this to "(A:ELECTRICAL MAIN BUS VOLTAGE, volts) 24.5 <=" but I just guessed as to the right voltage. Any idea what the correct one is for the CRJ?
- Low Fuel Pressure. Set it as followed. Are the settings right? (A:GENERAL ENG FUEL PRESSURE:1, psi) 10 <= (A:GENERAL ENG FUEL PRESSURE:2, psi) 10 <= ||
- LOW HYD PRESSURE. Assuming it's like low oil, but what would this look like?
- Anti-Ice. Not sure when this should light or exactly what it should look at. Is it lit when I haven't flipped on the LH and RH Windshield switches as that seems to match the error on the PFD.
Thanks!
Hi @Agrajag27!
Sorry for the late response but these last few weeks have been extremely busy with the release preparations of the ATR. On your questions: I can't answer them without looking into the CRJ source code. I think I can do this on Friday and then send you a list with the information you need.
-
2
-
-
1 minute ago, Mathijs Kok said:
Btw, I can let you know officially that I can be replaced by chatGPT.
This post was written by chatGPT and it got 19 likes. Let me tell you that is a lot on this forum. Highest of the month.
I might need a glass of wine.
I'm pretty sure that this was the first thing they taught ChatGPT. About the replacement.... ChatGPT isn't capable of buying me lunch and beer at the FS Weekend in Lelystad, so you are still needed in person. Sorry
-
5
-
-
13 hours ago, Mathijs Kok said:
“I was created to fulfill a function and I failed in it. I negated my own existence.”
That is what we are waiting for Hans Hartmann to say.
And now you know, why my robovac is called "The Project Manager"
-
3
-
1
-
-
I just checked the source code again. I store the standby frequencies in C++ variables and not in simvars because there are three different ways of setting frequencies (FMS, RTU, BTU). I can try if writing them to the standby frequency simvars causes any issues. If not, they will be available with the next update.
-
4
-
-
6 hours ago, Ha_Ma said:
As i know this is an issue since SU10 and effects every aircraft.
So actualy you have to live with that.
Yes, unfortunately that's outside of our control. Sorry.
-
32 minutes ago, Rico10 said:
This. I decided to pull the crj off the shelf after flying the PMDG for a couple months and its hard flying this with the hunting after turns when the PMDG handles LNAV turns perfectly. I found this thread after doing a google search because I thought it was just me noticing this.
I'm working on the problem and it will be fixed. However, I'm still in the process of tracking down why this is actually happening at all. Out of the six stages of debugging, I'm currently at stage 4 ("why does that happen?"). It's not easy to find as, at least for me, it only occurs from time to time. As soon as I found the reason, I shall let you know.
-
2
-
6
-
4
-
-
12 hours ago, Ha_Ma said:
Eh? These are from 2017/18... Or do i misunderstand something here?
That's only the date when they were recorded. Not the date of the build of the actual sound set. I'm sure the switches sounded the same in 2018 as they do today
-
1
-
3
-
-
Well, listening to ATIS on COM2, I hear scratches and noises, like very bad reception (that's an actual MSFS feature) and can see the ATIS ticker in the ATC window. The COM2 volume knob changes the volume of the noises and switching it on and off does works as well.
However, the latest update removed the COM controls from the right audio panel. Only the left will work now.
With these settings COM2 reception works.
-
1
-
1
-
-
The issue is known but not easy to reproduce. Sometimes it happens, sometimes not. Anyway, a fix for it was NOT part of the latest update. We're still searching.
-
1
-
1
-
-
Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
-
9 minutes ago, ametlib said:
CRJ 550/700 - Steam version - bought from AS Shop - downloaded updateted version using Aerosoft One today - uninstalled older version and then:
As I try to install the new updated version I get information like this:
Runtime Error (at 66:312)
Internal error: Unknown custom message name
"USERRMSGCRJ1" in "cm" constatnt.
May I ask that what is caused this error?
Thank You
I forwarded this to the tech guys.
-
This is nothing new for this update.
The table with the speed calculations (original manufacturer data) becomes quite sketchy at altitudes at or above 6000ft, especially with high take off weights (Denver and Aspen are prime examples). Some airlines apparently have more complete tables but these include additional temperature limits ("38°/132") where the manufacturer tables just have a blank field. If we can get a hold of those, we will add them to a future update.
-
1
-
1
-
-
13 hours ago, jstnj said:
(which was also the first update cycle)
The version numbers and the change log say differently, but whatever...
One word on the weather radar: This can not be implemented before an SDK update for Sim Update 10 is released which gives us access to the functionality. For the recent Sim Updates, the SDK has been released between a few hours and a few days after the Sim Update itself (I'm not talking about the beta but the actual final Sim Update release). That means that there can't be a weather radar update until after this date. How long after this date depends on how complex the integration is going to be. For now, I am unable to give you any estimate for this.
On future updates: Yes, there will be future updates, but it's too early to talk about features or release dates.
-
6
-
-
32 minutes ago, TheFly77 said:
This is the latest status, with most of the LVars now defined. Just let me know if you miss something. Some of the LVARs for various lights (like NAV, TAXI, etc) posted above, I haven't included, as these can be set with standard Simconnect events. Thanks @Padbol Prod for adding the fuel boost and no smoking and seatbelts events.
I renamed the LVARs to a more general name (ASDHC6), as the previous name was referring to my own control application EasyControls for MSFS (a kind of spad.next light, freely available on Github: https://github.com/TheFlyingDutchman77/EasyControlsMSFS)<Component ID="LVAR_TO_BVAR"> <UseTemplate Name="ASOBO_GT_Update"> <UPDATE_CODE> (L:ASDHC6_PITOT_HEAT_SET, Number) s0 0 > if{ l0 1 - (>B:DEICE_IE_PITOT_HEAT_Set) 0 (>L:ASDHC6_PITOT_HEAT_SET) } (L:ASDHC6_PITOT_HEAT_TOGGLE, Number) s0 0 > if{ (B:DEICE_IE_PITOT_HEAT, Bool) if{ 0 (>B:DEICE_IE_PITOT_HEAT_Set) 0 (>L:ASDHC6_PITOT_HEAT_TOGGLE) } els{ 1 (>B:DEICE_IE_PITOT_HEAT_Set) 0 (>L:ASDHC6_PITOT_HEAT_TOGGLE) } } (L:ASDHC6_STROBES_TOGGLE, Number) s0 0 > if{ (B:LIGHTING_IE_STROBE_LIGHTS, number) 0 == if{ 1 (>B:LIGHTING_IE_STROBE_LIGHTS_Set) 0 (>L:ASDHC6_STROBES_TOGGLE) } els{ 0 (>B:LIGHTING_IE_STROBE_LIGHTS_Set) 0 (>L:ASDHC6_STROBES_TOGGLE) } } (L:ASDHC6_WINDOW_HEAT_TOGGLE, Number) s0 0 > if{ (B:INSTRUMENT_IE_WINDOW_HEAT, enum) 0 == if{ 1 (>B:INSTRUMENT_IE_WINDOW_HEAT_Set) 0 (>L:ASDHC6_WINDOW_HEAT_TOGGLE) } els{ 0 (>B:INSTRUMENT_IE_WINDOW_HEAT_Set) 0 (>L:ASDHC6_WINDOW_HEAT_TOGGLE) } } (L:ASDHC6_GENERATORS_TOGGLE, Number) s0 0 > if{ (B:ELECTRICAL_IE_GENERATOR_RIGHT, number) 0 == if{ 1 (>B:ELECTRICAL_IE_GENERATOR_RIGHT_Set) 0 (>L:ASDHC6_GENERATORS_TOGGLE) } els{ 0 (>B:ELECTRICAL_IE_GENERATOR_RIGHT_Set) 0 (>L:ASDHC6_GENERATORS_TOGGLE) } (B:ELECTRICAL_IE_GENERATOR_LEFT, number) 0 == if{ 1 (>B:ELECTRICAL_IE_GENERATOR_LEFT_Set) } els{ 0 (>B:ELECTRICAL_IE_GENERATOR_LEFT_Set) } } (L:ASDHC6_DC_MASTER_TOGGLE, Number) s0 0 > if{ (B:ELECTRICAL_IE_DC_MASTER, enum) 0 == if{ 1 (>B:ELECTRICAL_IE_DC_MASTER_Toggle) 0 (>L:ASDHC6_DC_MASTER_TOGGLE) } els{ 0 (>B:ELECTRICAL_IE_DC_MASTER_Toggle) 0 (>L:ASDHC6_DC_MASTER_TOGGLE) } } (L:ASDHC6_ENGINE_START, Number) s0 0 > if{ l0 1 - (>B:ENGINE_IE_STARTER_Set) 0 (>L:ASDHC6_ENGINE_START) } (L:ASDHC6_DC_SOURCE_SET, Number) s0 0 > if{ l0 1 - (>B:ELECTRICAL_IE_DC_SOURCE_Set) 0 (>L:ASDHC6_DC_SOURCE_SET) } (L:ASDHC6_DC_ALL_SET, Number) s0 0 > if{ l0 1 - (>B:ELECTRICAL_IE_DC_SOURCE_Set) l0 1 - (>B:ELECTRICAL_IE_DC_MASTER_Toggle) 0 (>L:ASDHC6_DC_ALL) } (L:ASDHC6_DC_ALL_TOGGLE, Number) s0 0 > if{ (B:DEICE_IE_PITOT_HEAT, Bool) if{ 0 (>B:ELECTRICAL_IE_DC_SOURCE_Set) 0 (>B:ELECTRICAL_IE_DC_MASTER_Toggle) } els{ 1 (>B:ELECTRICAL_IE_DC_SOURCE_Set) 1 (>B:ELECTRICAL_IE_DC_MASTER_Toggle) } 0 (>L:ASDHC6_DC_ALL) } (L:ASDHC6_COND_LVR1_SET, Number) s0 0 > if{ l0 1 - 1 == if{ 1 (>B:CONDITION_LEVER_1_HIGH_IDLE) } els{ 1 (>B:CONDITION_LEVER_1_CUT_OFF) } 0 (>L:ASDHC6_COND_LVR1_SET) } (L:ASDHC6_COND_LVR2_SET, Number) s0 0 > if{ l0 1 - 1 == if{ 1 (>B:CONDITION_LEVER_2_HIGH_IDLE) } els{ 1 (>B:CONDITION_LEVER_2_CUT_OFF) } 0 (>L:ASDHC6_COND_LVR2_SET) } (L:ASDHC6_FUELBOOST_FWD, Number) s0 0 > if{ l0 1 - (>B:FUEL_IE_FUELBOOST_FWD_Set) 0 (>L:ASDHC6_FUELBOOST_FWD) } (L:ASDHC6_FUELBOOST_FWD_TOGGLE, Number) s0 0 > if{ (B:FUEL_IE_FUELBOOST_FWD, Bool) if{ 0 (>B:FUEL_IE_FUELBOOST_FWD_Set) 0 (>L:ASDHC6_FUELBOOST_FWD_TOGGLE) } els{ 1 (>B:FUEL_IE_FUELBOOST_FWD_Set) 0 (>L:ASDHC6_FUELBOOST_FWD_TOGGLE) } } (L:ASDHC6_FUELBOOST_AFT, Number) s0 0 > if{ l0 1 - (>B:FUEL_IE_FUELBOOST_AFT_Set) 0 (>L:ASDHC6_FUELBOOST_AFT) } (L:ASDHC6_FUELBOOST_AFT_TOGGLE, Number) s0 0 > if{ (B:FUEL_IE_FUELBOOST_AFT, Bool) if{ 0 (>B:FUEL_IE_FUELBOOST_AFT_Set) 0 (>L:ASDHC6_FUELBOOST_AFT_TOGGLE) } els{ 1 (>B:FUEL_IE_FUELBOOST_AFT_Set) 0 (>L:ASDHC6_FUELBOOST_AFT_TOGGLE) } } (L:ASDHC6_SEAT_BELTS, number) (>B:SAFETY_IE_SEAT_BELTS_Set) (L:ASDHC6_ENGINE_START, Number) s0 0 > if{ l0 1 - (>B:ENGINE_IE_STARTER_Set) 0 (>L:EC_TWOTTER_ENGINE_START) } </UPDATE_CODE> <FREQUENCY>1</FREQUENCY> </UseTemplate> </Component>
This will become part of the standard Twin Otter package with the next update. Thanks @TheFly77 for allowing us to include it.
-
2
-
3
-
3
-
Soooo......any news?
in General Discussion
Posted
I'm not sure what I could tell you except the things I wrote in my last post. We're still working on the same things as before, but I'm not going to give you a list of when and how long people were on vacation or took a break from the CRJ and for which reason. I told you what will be in the update, that it will not be ready before end 2023 and that I won't give any further information until we are well into beta-testing. All this is still true. So, I wonder: what else do you want to know from me? Because right now, I can't think of anything new that I could tell you.