Tornado GR1 new update
Printed From: Just Flight Forum
Category: Just Flight Products
Forum Name: Tornado GR1
Forum Description: Discussion area for the Tornado GR1
URL: http://forum.justflight.com/forum_posts.asp?TID=32018
Printed Date: 20 Apr 2024 at 2:01am
Topic: Tornado GR1 new update
Posted By: Morti
Subject: Tornado GR1 new update
Date Posted: 05 Jan 2018 at 7:35pm
|
Hi, FSX boxed version Got a email to say about new service pack 5 was ready to download. I uninstalled the older version and downloaded latest exe from my account. I reinstalled my previous repaints and now I'm unable to turn on the nav screens in rear cockpit. They just stay black. The map displays okay. Any advice? |
Replies:
Posted By: Morti
Date Posted: 05 Jan 2018 at 7:56pm
|
Front cockpit missing a gauge (red arrow:) https://1drv.ms/i/s!Ai3u50hquI_shskMabGh1ilpfkHUZw Rear Missing gauge ?? red arrows and the Nav screens wont turn on https://1drv.ms/i/s!Ai3u50hquI_shskLzlysa5SQd5YWnw |
Posted By: petesmiffy
Date Posted: 05 Jan 2018 at 8:37pm
|
In my case Left Screen works but switching on the Right leads to CTD |
Posted By: Morti
Date Posted: 05 Jan 2018 at 8:51pm
|
HUD not working nither! any ideas? |
Posted By: Martyn
Date Posted: 05 Jan 2018 at 9:42pm
|
I've just installed the latest version of the Tornado into a fresh copy of FSX:SE and couldn't reproduce these issues. The warning radar and HUD work in the front cockpit, and after using the performance configuration tool to enable all of the rear cockpit and gauges, they are all working OK too (load correctly no CTDs etc). The rear cockpit screen in the bottom right that is highlighted in your image is not simulated/included in this product. If you still encounter these issues after uninstalling, ensuring that no files are left over in the SimObjects\Airplanes folder, and then installing the latest version again (before modifying any files/adding any extra liveries), then please contact the support team and we'll investigate. Thanks Martyn ------------- Martyn Just Flight Ltd |
Posted By: Bjoern
Date Posted: 06 Jan 2018 at 12:58am
|
I can reproduce the issue. GR.1 SP5, fresh installation into FSXSE on Windows 10. All the gauges successfully register at first start. Start a flight in the aircraft, select "Ready For Takeoff" from the menu. The engines start, but all displays (E Scope, HUD, RWR, TV displays) stay off. Granted, I didn't read up on how to turn them on yet, but being "ready for takeoff" should imply that everything's up and running.  Would be great if you could look into this. Not sure whether the options set in the Configuration Utility ("texture_VC" folder) have something to do with this or not. Couldn't find any documentation on it (the manual only deals with the tool's texture management part). If there'll be another update or hotfix, please silence the highly annoying default fuel pump sound by having this in the sound.cfg by default:
|
Posted By: Morti
Date Posted: 06 Jan 2018 at 1:42pm
|
Martin, I not tried to uninstall and start a fresh install yet.. Will try this (FSX boxed) over the weekend. I use both FSX boxed and FSX SE. Morti |
Posted By: Morti
Date Posted: 06 Jan 2018 at 1:47pm
|
Bjoern wrote:Posted By: tucanto
Date Posted: 06 Jan 2018 at 1:55pm
|
I too have just installed update 5, now Hud is not and rear displays not operating I have saved them to on in the configuration tool. This is an update ?? |
Posted By: Joe Whiskey
Date Posted: 06 Jan 2018 at 4:00pm
| P3Dv4 fresh install. Unable to get anything working in the backseat. The moving map looks like a rear parking camera... I hope this will be fixed as I had high hopes for the P3Dv4 version. |
Posted By: Morti
Date Posted: 06 Jan 2018 at 9:28pm
|
FSX fresh install As request no added testures ... same result. |
Posted By: Uncle Bucc
Date Posted: 06 Jan 2018 at 10:43pm
|
I have been having the same experience. Configured the cockpit(s) and no HUD and black screen in the Navigator/Weapons System Officers position. Unable to configure weapons loadouts, fuel loads and flight plans.  |
Posted By: Bjoern
Date Posted: 06 Jan 2018 at 10:50pm
|
Further bugs found so far: - CSAS BITE check can not be conducted. Test button does not illuminate after pressing, neither on 2D panel nor in the VC. - CSAS "PREFLT/1ST LINE" switch bitmap disappears when in "1ST LINE" position - Manual/Checklists: In the "Initital Checks" list, the ignition switch must be set to off, but there's no item in the "Starting Engines" list that requires the switch to be on again. Without ignition, no engine start. And I still don't get any HUD, TFR, TV or RWR displays, despite following the checklist to the letter. |
Posted By: DaveG
Date Posted: 07 Jan 2018 at 12:09pm
Yep, same issue here, using P3dv4.1 HUD, TFR & TV screens are working for me though. |
Posted By: Morti
Date Posted: 07 Jan 2018 at 12:57pm
| Checked the tornadogr1.cfg in panel and it only has one line in it. |
Posted By: Martyn
Date Posted: 07 Jan 2018 at 5:23pm
|
As per my post above, if you are encountering any missing gauges then please submit a support ticket so we can collate all of the information and identify the cause. If you are using FSX:SE then please also ensure that you have the legacy version of SimConnect installed ( https://www.justflight.com/support/flight-simulator-x-steam-edition/384bffb" rel="nofollow - https://www.justflight.com/support/flight-simulator-x-steam-edition/384bffb ) Thanks Martyn ------------- Martyn Just Flight Ltd |
Posted By: Martyn
Date Posted: 07 Jan 2018 at 5:24pm
Please ignore the cfg file located within the panel folder. The file has been relocated to AppData to allow people to move the Tornado aircraft folder outside of the standard SimObjects folder. Thanks Martyn ------------- Martyn Just Flight Ltd |
Posted By: Merlin59
Date Posted: 07 Jan 2018 at 6:51pm
| Add me to the list. No HUD or rear screens at all. Just got this and it looks good but as is unflyable. Hope it's fixed soon. |
Posted By: Martyn
Date Posted: 08 Jan 2018 at 8:24am
|
If you haven't already done so, please submit a support ticket as we need to gather information on simulator versions etc, so we can attempt to reproduce the issue here, send you gauges to test etc. EDIT: We will shortly be sending some replacement gauges to those of you who have contacted us. If they resolve the issue then we'll update the installer ASAP. Thanks Martyn
------------- Martyn Just Flight Ltd |
Posted By: Martyn
Date Posted: 08 Jan 2018 at 9:53am
Unfortunately this is another one that I can't reproduce.
Thanks Martyn ------------- Martyn Just Flight Ltd |
Posted By: Morti
Date Posted: 08 Jan 2018 at 1:21pm
|
Hi, I got your email.. but unable to install files sent and check until this evening. Was called into work this morning ..sorry. Should be able to about Thanks Morti |
Posted By: Bjoern
Date Posted: 08 Jan 2018 at 4:50pm
Reset the aircraft state to cold and dark. External power was still connected; switched on the battery, did a successful AFDS BITE test, but again, no reaction when pressing the "TEST" light.
Yes.
Yes. I, however, found out that I can get the CSAS BITE test started by starting one engine, pressing the "TEST" button (will not illuminate) and immediately the "(CSAS) ENGAGE" button (test will begin). Then, I can complete all items on the checklist except the last one. The second to last item automatically marks as complete and the "GO" light, contrary to checklist instruction, automatically illuminates. Pressing the "TEST" button to extinguish the blinking "TEST" light has no effect. The "SPILS BITE" light also keeps blinking. Therefor, I am unable to complete the CSAS BITE TEST. I can submit a ticket with all the bugs I've found so far if it helps, although I think that posting the bugs here in the forum avoids a flood of tickets containing essentially the same things. P.S: If you're taking a look at the CSAS test gauge logic, could you maybe add an "auto cycle trims" button or increase the trim surface control acceleration while in test mode? Cycling the emergency trims and the normal trims through their full range is quite time consuming because of the small increments. P.P.S: If the Tonka used XML gauges, I could help you out in hunting down the exact cause of those bugs, but with C++ gauges, my hands are tied. |
Posted By: Roebuck
Date Posted: 08 Jan 2018 at 5:36pm
|
CSAS BITE can only be performed after first engine start (Which should be the right hand engine) as per the real aircraft. Regards, Roebuck
|
Posted By: Roebuck
Date Posted: 08 Jan 2018 at 5:39pm
|
Also, The CSAS Test is normally carried out every 7 days or after a snag occurs. So at least we don't have to go through the toils and tribulations of the BITE every flight ;). Regards, Roebuck.
|
Posted By: Morti
Date Posted: 08 Jan 2018 at 6:26pm
|
Hi Martin, Further to my ticket ..i have sent 3 replies to Craig.. regarding these issue. Just so u know what going .. In my emails I said I could load flight plan .. but i managed to do so once air born. And HUD didn't more which it DOES on my last test!! My AI at RAF Marham must have been complaining to ATC !!! Whilst ideas checking! I did one last test where i changed and ticked gauges which was unticked in configuration tool and reloaded SIM and they seemed to work.. then after 5mins of flying crash to desktop. With the 2D panels are we supposed to see the main pilot view with HUD as a 2D panel or just in VC pilot veiw? Thanks MORTI |
Posted By: Martyn
Date Posted: 09 Jan 2018 at 9:58am
|
A new installer is now available in your account, which should hopefully address the missing gauge issue that some of you were encountering. Thanks Martyn ------------- Martyn Just Flight Ltd |
Posted By: Bjoern
Date Posted: 09 Jan 2018 at 1:08pm
|
In case anybody's wondering: The gauges in the "panel" folder are the only things that were changed. The HUD, TFR, RWR and TV displays work again. Thanks! But the framerate... I can turn down everything in the configurator, use the low-poly cockpit, the 2048 px textures, etc... and my framerate over land alternates between 9 and 14 (normally 30). If I disable all gauges in the panel.cfg, framerates return to normal - or at least to what is normal for a model with 350000+ polys (~27 FPS). Are the gauges drawn with GDI+? If so, this would be a perfect explanation for their rendering performance as the method is notorioulsy resource-intensive most of the time. |
Posted By: Martyn
Date Posted: 09 Jan 2018 at 1:53pm
|
All glass/digital displays are coded using GDI+. Here was my reply to a similar post on SOH: It'll always be a demanding product due to its complexity but you can find more information on optimising performance (a tool is included for that) on the support page. In P3D v4, using a fairly modest PC, I get approx 50-60 FPS in the VC and 90+ FPS in the exterior view. If you are using a modern gaming PC and are seeing less than that, then it might be worth getting in touch with our support team. I see a similar FPS range in FSX:SE with the rear cockpit and 4096 textures enabled when using a 7-8 year old gaming PC, but it's slightly smoother in P3D v4. If you haven't already done so, it's also worth adjusting the gauge refresh rates (see the support section for more info). If you are unable to get satisfactory performance then we're of course happy to provide a refund/exchange. Thanks Martyn
------------- Martyn Just Flight Ltd |
Posted By: Bjoern
Date Posted: 09 Jan 2018 at 2:45pm
That explains it. I'm not sure why, but I never had any luck with aircraft using GDI+ for gauge rendering. Each of them always dragged down performance by a good margin. Could be the anti-aliasing or the fact that it's entirely software rendered, I don't know.
As I've said, I've used the tool for decreasing gauge refresh rate to the bare minimum, switch to the simplified cockpit model, cut textures down to 2048 pixels, turn off effects, etc...nothing really helped.
It all depends on how you've configured the simulator and I am convinced that it is indeed possible to get high frame rates in the Tornado if you decrease other overhead (terrain, weather, AI traffic). But I'm mostly an airliner guy and my sim is configured for that.
Well, that depends. I figure any further, large performance optimizations are not part of the development roadmap for the Tornado, right? If that's the case, I'd go for an exchange and try my luck with a different model from JF's lineup. Thanks for the offer!
|