l0k1 / mig-21bis Goto Github PK

Add a seperate view that focuses in on the radar screen.

Suggestion from discord chat by Sierra.

Upon further reading of the manual, it appears that the MSL-GYRO will completely disable the GYRO portion of the gunsight, leaving it centered (with respect to the angular setting).

It's a hot mess.

Also, it needs a lead computing gunsight, and the other aiming reticle.

when I try to use my mig-21bis, I mention that I cannot turn my view in helicopter and chase views. so I wish the developer can fix this problem

Window visible above.

This error message is present at startup. The cause needs to be id'd and we should get this message out of there.

Currently there are two "Left" entries

Need to transmit the nosewheel angle over MP

In the AFALCOS implementation, there is a typo in the definition of W2: line 152 in

        me.W2 = me.W2 + (-me.SL1 * me.SL3 + me.C7 * me.SL3) * me._getP() + 

-me.SL1 * me.SL3 should be -me.SL1 * me.SL2 instead.

Corresponding code from the original paper, just in case:
W2=W2+(-SL1*SL2+C7*SL3)*P+(1.-SL2**2)*Q-(SL2*SL3.C7*SL1 )*R

Every autopilot function could use a nice retuning - they are sloppy after the multitude of FDM changes.

Should include all instruments, and all switches should be clickable - with implementation happening as systems get added.

So far, hull has been reworked, cockpit layout has been reworked, and work on the front panel and gunsight is ongoing.

Currently, the switch only works if set in the "OUTBOUND" position, and searches for another nearby NDB to switch to.

How it should work AFAIK:
If switch is set to outbound, and the channel is odd and not 9, and the gear is down: upon flying over the outer NDB marker with some degree of accuracy, the radio automatically switches to the channel indicated on the ARC dial (2,4,6 or 8) - the roman numeral I is for tuning slow (8 secs), and the II is for tuning fast (4 sec).

If switch is set to inbound, and the gear is down: the ADF is tuned to what is indicated on the knob.

The missile smoke and missile explosions appear both at the pylon position and the missile position.

Needs to be updated from https://github.com/NikolaiVChr/flightgear-saab-ja-37-viggen/blob/master/Aircraft/JA37/Nasal/vector.nas

The title says it all.

I have the following error when firing a Kh-66:

  269.56 [INFO]:nasal      multi-threading error:
  269.56 [INFO]:nasal      No such member: get_uBody
  269.56 [INFO]:nasal      /home/colin/flightgear/Aircraft/MiG-21bis/Nasal/guided-missiles.nas
  269.56 [INFO]:nasal      3515
  269.56 [INFO]:nasal      /home/colin/flightgear/Aircraft/MiG-21bis/Nasal/guided-missiles.nas
  269.56 [INFO]:nasal      2873
  269.56 [INFO]:nasal      /home/colin/flightgear/Aircraft/MiG-21bis/Nasal/guided-missiles.nas
  269.56 [INFO]:nasal      2106

If I did not mess up, my radar was in beam mode (on radar panel: left switch up, middle switch down, right switch up).
When firing with radar turned off, the error doesn't occur and the missile works correctly, but is of course unguided.

should be limited to directly behind the launcher.

Copied from wiki-article (https://github.com/l0k1/MiG-21bis/wiki/Navigation): the gyro compass is implemented using FG's property rules system, which may cause some issues with accuracy if frame rate is very low. this should be ported to use jsbsim instead, however this is low priority for me at this time.

As reported by @legoboyvdlp

In my opinion it should just be replaced entirely using particles.

ripple fire works ok

single fire works on the 1st instance (doesn't matter which pylon is selected) but throws up this error after launching the 1st/hitting the target:

Nasal runtime error: non-objects have no members
at MiG-21bis/Nasal/payloads.nas, line 371

no more errors show in the logs, selecting ripple fire doesn't work either

Preventing to have to restart FG to get full amounts of rounds back.

Should only work when wow.

Per @Kokos345 on the discord server, an F-15 flying behind him failed to appear on the RWR.

These are very important for a high fidelity aircraft. These should also be implemented in JSBSim.

Currently the dead reckoner is written using FG's native property rules, which run at frame rate. Switching from property rules to JSBSim will increase accuracy, especially on computers with low frame rate.

Currently the gyro compass is written using FG's native property rules, which run at frame rate. Switching from property rules to JSBSim will increase accuracy, especially on computers with low frame rate.

Every autopilot function could use a nice retuning - they are sloppy after the multitude of FDM changes.

• Drag is too low at sea level - almost supersonic is possible.
• Yaw is... just... yeah.
• RWR needs a good talkin' to.

When changing any radio frequencies in the MiG-21bis, there should be a delay of some seconds.

The FAB-100 can have up to 4 bombs on the inner pylons, and the R-60 can have 2.

They are wrong.

• remove close()
• dont recreate dialog every time its called

In MiG-21-set-common.xml, line 1739

<file>Aircraft/MIG-21bis/Nasal/tacview.nas</file>

should be

<file>Aircraft/MiG-21bis/Nasal/tacview.nas</file>

(incorrect case for the i in MiG).
Causes the file to fail to load, and a bunch of nasal errors in console, on case-sensitive file systems.

This is relating to the help dialog box that shows keyboard bindings.

When radar beam mode is enabled, sometimes the contact marker and text is not hidden. When beam mode is exited, the contact marker stays in place.

dead reckoner should be hardly moving in the above image

In Nasal/armament-locking.nas, line 200 loads a model which doesn't exist:

objModel.getNode("path",1).setValue("Aircraft/MiG-21bis/Models/tgtsphere.xml"); # this is the model to be loaded.

This generates a constant flow of Error in reading file : file not handled messages in the console.

Per pdf page 29 of the MiG-21bis manual. For instance, UB-32 pods should only be allowed on the inner pylons.

Consider adding a link from readme.md to http://wiki.flightgear.org/Mikoyan-Gurevich_MiG-21 for documentation.