4.35 released: what does it changes for us:

[Rufus]

Yes - got that...I was more concerned about neither one of them launching as I was checking things out!  Got it sorted as detailed.

[Focaldesign]

MFDE and YAME will not launch in 4.35.

It appears we will not be able to extract STBY ATT, VVI, AOA, Mach Meter, ALT, Horizon,EHSI either if we can't get MFDE or Yame to work. A little disappointed.

I have RTT for DED, RWR and MFDs and YAME for all the rest without issues.
RTT works, and Yame with the already known workaround that was needed for 4.34.

[viper26]

I have confirmed that MFDE works.  The only issue I have right now is trying to figure out how this RTT works.  I launch it and get a big and small square with a red X in the middle of each.  Not sure what to do next. 

[Rufus]

There is a configuration file you have to set up - as far as I can tell, the X'd squares just mean the Client is running and not getting anything from SM yet...I wish they would just put up a blank MFD like MFDE does...

...you have to specify the coordinates to display the MFDs at in this Config file - how you do this for multiple individual screens is beyond me currently, but you must be able to do it somehow.  I have no idea how this will work in conjunction with projectors, but it seems like any time you change you center display (or it's resolution) you may also have to adjust your MFD coordinates to put them in the newly proper places.

I hope that in the future they incorporate the ability to simply drag and drop them like MFDE has...

[viper26]

Is this config file in the User Configuration folder?

[Nomad]

It’s in the RTT Client ini file.

[viper26]

I got the .ini file updated and the MFDs are correctly aligned with the Red Square and Circle.  I launch RTT client first then launch the game.  When I'm in the pit my screens go blank put no MFDs come up.  Here is my copy of the .ini  I thought it was pretty intuitive but I may have missed something. 

### RTT Client v3.2
### by Dunc, 2020/12

# The preferred renderer to use:
# 0 = SDL2: pick automatically
# 1 = SDL2: Direct3D 9
# 2 = SDL2: Direct3D 11
# 3 = SDL2: OpenGL
# 4 = SDL2: OpenGL ES
# 5 = SDL2: Software
# 6 = SFML: OpenGL
RENDERER = 0

# RTT Client can connect to RTT Server via network, or read the
# local BMS RTT directly, w/o the need for running RTT Server.
# 0 = RTT Client read the local BMS RTT directly
# 1 = RTT Client will connect to RTT Server
NETWORKED = 0

# ONLY IN USE IF "NETWORKED = 0"!
# How often should the client poll the RTT are to check for changes?
# The higher the value, the more GPU/CPU load you generate.
# Note that this value does NOT affect the "smoothness" of the
# display animations. The display can not draw more frames than
# BMS is currently exporting to RTT (which by default is BMS FPS / 2).
FPS = 30

# ONLY IN USE IF "NETWORKED = 1"!
# The IP address and port where the server is running.
# Supports both IPv4 and IPv6.
HOST = 127.0.0.1
PORT = 44000

# ONLY IN USE IF "NETWORKED = 1"!
# If you use the client on a networked PC (not locally), it is
# possible not only to receive the RTT images, but also the "normal"
# shared memory areas. Just enable the ones that you want to access
# remotely, it will be created on the client side for you.
DATA_F4 = 0
DATA_BMS = 0
DATA_OSB = 0
DATA_IVIBE = 0

# These are the displays that we can render on the client. For configuration,
# simply pre- or postfix these strings with "USE_" or "_X", "_Y", "_W", "_H",
# "_ONTOP", like in the examples below.
# HUD
# PFL
# DED
# RWR
# MFDLEFT
# MFDRIGHT
# HMS

# The RWR is usually displayed without any grid/cirle lines (so you can use e.g.
# your own nice glas etchings). However, if you want some (very basic) RWR grid
# to be overlayed on the RWR, set the following to 1:
RWR_GRID = 0

# Which RTT displays do you want to show on the client side?
USE_HUD = 0
USE_PFL = 0
USE_DED = 0
USE_RWR = 0
USE_MFDLEFT = 1
USE_MFDRIGHT = 1
USE_HMS = 0

# Each display that you want to see must have at least TWO config
# entries: X and Y coordinate (of the upper left corner).
# Additionally, you can specify the width W and the height H of the
# display. If you do not specify width and height, the original
# size of the RTT will be used (but the "no connection placeholder"
# will not show the correct size until the server is actually sending
# valid data). Note that the X/Y coordinates originate in the upper
# left corner of your MAIN windows screen. So you can have negative
# coordinates if you e.g. use a monitor to the left or above the main
# screen.
# Furthermore, RTT Client can *try* to render displays "always on top",
# (ONTOP = 1, default 0) allowing you to overlay displays e.g. on the
# main BMS view.
# Examples:

MFDLEFT_X = -2970
MFDLEFT_Y = 85
MFDLEFT_W = 964
MFDLEFT_H = 1007
MFDLEFT_ONTOP = 0

MFDRIGHT_X = -1222
MFDRIGHT_Y = 118
MFDRIGHT_W = 989
MFDRIGHT_H = 990
MFDRIGHT_ONTOP = 0

[viper26]

Found this on the BMS forums and it fixed my issue:  Go to C:/Falcon BMS 4.35/user/falcon bms.cfg and search for this :
set g_bExportRTTTextures 0 change 0 to 1.

[Rufus]

I think I read that and read right over/past it...but now that I see you post it makes far more sense...

...should think this should be default setting, seeing as how RTT is supposed to be the new hotness?

[Red Dog]

post 23 explains why

And I told you guys to have a look at the RTT chapter in the tech manual didn't I?
You really made it hard on yourselves on this one.

[KK]

We have RTT and we also have RFM (Read a f* manual)

The manuals from Red Dog are a great read.
Especially his BMS COMMS and NAV MANUAL
is my favourite. This is a must for every one.

[AlbertJ]

Today the latest 4.35 version of BMS has been released:

What it changes for pitbuilders:

- mandatory use of RTT now for display extraction as older BMS native version of extraction are not supported anymore
- although Yame was kinda hard to get to work with 4.34, YAME work in the same way in 4.35

- Anti ice implemented (right side 3 position sw needed for anti-ice)
- Gear solenoid & Down lock release button implemented (gear panel)
- Anti-skid implemented  (gear panel, need a 3 post mag switch mag to PB and guarded to Anti-skid)
- JFS START 1 implemented  (need a 3 position mag switch for JFS)
- Arrestor system implemented at non generic airbases (hook switch)
- better implementation of the alternate gear system (pull handle and reset button)
- Canopy switch implemented (3 pos) and protected by Spider
- Spider switch implemented (pressure switch starts pressurisation)
- Brake channel system completely implemented (2 channels redundant from FLCCS - need 2 pos switch for CHAN1and 2 on gear panel)
- FLCC branches are true quad and not a single one anymore , they can fail independently
- Taxi light / landing light implementation (need a 3 pos switch)
- Seat Adjust Up/ Down (right side wall)
- knobs now assigned to a analogue axis will register movement (COM1, COM2, etc etc).
- More steps for INT lights knobs

-AIC, Oded, Martin's software, Simshaker, Yame and TIR remains compatible


Out of the blue the above are the stuff that may need to be updated in your cockpits. For the rest, please refer to the BMS forum and enjoy the latest Opus

@Red Dog
 
Do you know if there will be an small update regarding the AIC lightbits?
Till 4.34 the FLCS PWR indicator on the test panel was only using one lightbit, but for 4.35 we now need 4 separate lightbits.

Today I discovered during a rampstart that the indicator will not light up at all with the FLCS switch in test position.

[Red Dog]

yes and more

The 4 branches indeed have their own bit and the gear solenoid was added amongst other features.
I guess Falcas will have to update his website with the newest version of AIC. Don't know when he plans to do that.

I'm sure it will be done when he actually also update WDP and MC which haven't been updated for 4.35 public as far as I know

[Marvin]

yes and more

The 4 branches indeed have their own bit and the gear solenoid was added amongst other features.
I guess Falcas will have to update his website with the newest version of AIC. Don't know when he plans to do that.

I'm sure it will be done when he actually also update WDP and MC which haven't been updated for 4.35 public as far as I know

He already has it done.  We've been using it for a while.  I guess he just needs to upload the link.

[jjbravo]

Don't want to be rude, but this is a F4ToPokeys Thread, not AIC 

F4ToPokeys has been updated with all the new flags.