Jump to content

Recommended Posts

Posted

Hi, could everyone from RAZBAM explain what are the actual topics and what are the next steps ?

 

The last changelog was very small for the M-2000C and there are still many things to do.....:weight_lift:

 

 

Thanks in advance.....

Ryzen 36000 / RTX2070 OC / 32 GB DDR4 @ 3600 Mhz CL. 16-19-19 / Thrustmaster T1600 - TWCS Throttle / Track IR-5 / LG 34" @ 3440 x 1440 / Windows 10 64 Bit

Posted

They're busy finishing NAV system and killing criticals and worse bugs... I suppose later we will see less critical bug killing, like bullseye VTB display, AAR tanker speed... and to implement some minor systems like contrameasure programmer, MWS maybe...

 

And campaing and training missions are on the way...

Posted
like bullseye VTB display

 

Is that the lack of bullseye coords on the mfd? No winder I couldn't find it. It makes life hard not having it.

I don't test for bugs, but when I do I do it in production.

Posted
Is that the lack of bullseye coords on the mfd? No winder I couldn't find it. It makes life hard not having it.

 

Not lack but currently WIP or bugged:

 

the digits displayed at left botton like XXX/XXX are the vector...

 

Default reference point is own aircraft, then they display course relative to your nose and range to TDC (IIRC it's inverted from US displays, they show first range and then course)

 

BUT if you select with "N" switch (located at left border of VTB) any waypoint, you wouldn't have self-reference but from selected WP, this way, if you have a WP at bullseye you got that important information ;), but now only is half implemented and not showing real values.

Posted

Perhaps this is not a bug just bad mission design. You must set which waypoint is the bullseye in mission editor. Have you (or mission author) done this?

Posted
Perhaps this is not a bug just bad mission design. You must set which waypoint is the bullseye in mission editor. Have you (or mission author) done this?

 

Yes tried, and bug confirmed and acknowledged. We just have to wait.

Mirage fanatic !

I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2.

Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi

Posted

Thanks for the feedback !

 

Could some please explain what is "bullseye" and how it works ?

 

Thanks in advance....

Ryzen 36000 / RTX2070 OC / 32 GB DDR4 @ 3600 Mhz CL. 16-19-19 / Thrustmaster T1600 - TWCS Throttle / Track IR-5 / LG 34" @ 3440 x 1440 / Windows 10 64 Bit

Posted

It's the reference point used by AWACS to give hostile's coordinates.

It's polar coordinate: Azimuth/ distance from reference point.

But on M-2000 the radar scope display distance/ azimuth of TDC cursor.

 

You need to to place a waypoint on Bullseye and select it with "N" button on top left of radar scope.

 

Currently the coordinates are wrong and the system needs to be fixed.

Mirage fanatic !

I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2.

Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi

Posted

OK....thanks for this explanation.

Many new stuff for me (beginner). Think i need a navigation course.

Is there are Video available to demonstrate the basic navigation items ?

 

Thanks

Ryzen 36000 / RTX2070 OC / 32 GB DDR4 @ 3600 Mhz CL. 16-19-19 / Thrustmaster T1600 - TWCS Throttle / Track IR-5 / LG 34" @ 3440 x 1440 / Windows 10 64 Bit

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...