Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 [2]   Go Down

Author Topic: fokker g1  (Read 484 times)

0 Members and 1 Guest are viewing this topic.

denko9001

  • member
  • Offline Offline
  • Posts: 63
Re: fokker g1
« Reply #12 on: February 10, 2019, 07:50:27 PM »

Well, believe or not...
But the bug I have described earlier is still valid.

no full quotes!

Does this mean that the both CX's can't be flown unless you turn the setting off? If I copy a cockpit file from another biplane, rename it, and put it in the cockpit folder for the CX (just like the G1) it should work.
Logged

denko9001

  • member
  • Offline Offline
  • Posts: 63
Re: fokker g1
« Reply #13 on: February 10, 2019, 07:51:56 PM »

Again, I do not have this problem in my master install, I can't reproduce this error. I have a perfectly working cockpit without any alterations.
Therefore I do not consider this a general issue.

Do you have any additional mods or JSGME mods activated?
I have stabilizers for all aircraft in jtw, tga, waw and dof active but those don't do anything you can't do in musketeer already. I will try disabling them.
Logged

SAS~vampire_pilot

  • SAS Team
  • member
  • Offline Offline
  • Posts: 3346
  • The man of a million fixes
Re: fokker g1
« Reply #14 on: February 10, 2019, 10:05:57 PM »

that stabs JSGME is either 3rd party or long outdated. stabs for all is available by default in BAT, no need to add anything.
Logged

Dimlee

  • member
  • Offline Offline
  • Posts: 540
Re: fokker g1
« Reply #15 on: February 11, 2019, 01:48:49 PM »


Does this mean that the both CX's can't be flown unless you turn the setting off? If I copy a cockpit file from another biplane, rename it, and put it in the cockpit folder for the CX (just like the G1) it should work.

All three aircraft I mentioned can not be flown unless you turn the setting off.
Again, there might be more aircraft affected by this bug.
There is a slight chance that the bug is my own "fault"... But it was in CUP and it appeared again in BAT and I tried to keep all my installations clean and not to play with files, except adding a couple of new maps.
It would be interesting to know, does this error happen with other users?

As for cockpit files replacement, sorry, I know nothing about that.
Logged
Pages: 1 [2]   Go Up
 

Page created in 0.057 seconds with 25 queries.