Jump to content

johnjar

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by johnjar

  1. Under the General menu Get new plane is set to Right Ctrl + Right Shift + Tab. I can not get it to work in a quick start mission ( Runway Start ) or in multiplayer. I have tried changing the keyboard command and assigning a joystick button and neither will work. I read someone wrote exit the cockpit first but I don't know how to exit. I know you can not eject. I have also tried the immoral setting. I have also tried the auto crash recovery. I can not get anything to work. Is there a special key command to respawn in multiplayer? Thanks to all !!
  2. Will you be adding the AH-64D? Is it even needed? I copied the AH-64D lines from the original SnapViews.lua and pasted them into your version of SnapViews.lua. I did not find any lines for the AH-64D in the Server.lua. Please, let me know what you think. Thanks for helping!
  3. When I wrote "blanking" I meant the MPD's were blank. I listened closer and the engine noise does change. Its just hard to hear over the "Rotor RPM low" warning. The track file "No changes Working as you wrote" I used the keyboard commands. Yes it works as you wrote with the APU on or off. The track file "Works all power lever keyboard setting cleared" I used the throttle on my HOTAS. To get it to work I had to clear all of the keyboard setting related to the Power Levers. Then it again worked as you wrote. So maybe I had some control set more than one time. I left well enough alone and stopped investigating. Please, check to see if the real AH-64D MPD's and IHADSS work this way and make changes as needed. I will be surprised if they do. Any way I am glad to get it working with my HOTAS. Forgive my slowness, I finally figured out what you meant by a "Track". Thanks again to all for helping! No Changes Working as you wrote.trk Works all power lever keyboard settings cleared.trk
  4. Oh I just noticed KGILLERS 3, there is no change in the engine noise.
  5. My HOTAS is a Logitech Space Flight X-56 advanced control flight system. I do not know when these problems started. But I know they were not happening when I first received this module.
  6. I found out that the problem is caused by the Power Lever Smoothly Increase and Power Lever Smoothly Decrease settings. The video I uploaded shows the MPD's go blank as the two levers reach the top. I could only show the bottom to top lever movement one time to keep the file size under 5 M. As the levers are moved bottom to top and the cycle is repeated, the MPD's blank near the bottom and turn on near the top of the travel. At times this cycle must be repeated several times before the blanking will begin. This will happen using the keyboard also. (Num - is Decrease and Num + is Increase) If I program the throttle on my HOTAS (Or any of the Rotaries) to these keys, I get the same blanking as they are moved. Also note the MPD's are dim when first turning on and gradually get brighter. This does not happen when they turn off. (Instantly blank) I do not know if it can be seen in the video. In the menu of Axis Settings the Power Levers Both has a different problem. Any time it is mapped to my HOTAS Throttle or any Rotary the MPD's go blank a few seconds after the flight is started. Then there is no way I have found to turn them back on. This is the problem I first reported in this post. Thanks to all for helping! MPD Blanking.MOV
  7. I found this problem with the AH-64D. The instant action mission “Runway Start” and the training mission Lesson 3 “TSD Navigation” both have this problem. Others may also have it I have not checked every one. The MPD’s and the “IHADSS“ are displayed as the mission starts. Then after a few seconds they all go blank. This happens for the pilot and the gunner at the same time. The training mission continues and high lights the required buttons to be pressed. The training will continue as if the displays can be seen. The complete training can be finished with all displays blank. My screen is 1920 x 1080. Monitors is set to “Screen 1” and full screen in selected. I have also done a full DCS repair using the slowest option. It did not help. I have not uninstalled and reinstalled the module. I do not want to reinstall DCS World. Instead I am writing this in hopes to get a solution. Let me know if there is any more information I can provide. Thanks to all for your help!
  8. Hey thanks ! That is something I did not know. It should make things much easier. Again thanks to all.
  9. This problem is with both the pilot and the CP/G keyboard settings. I can save a file and it appears to have saved. Then when I try to load it the file name is not there. It says "The file can not be found". Then if I exit the simulator and check the folder for the file it is really not there. So it was never saved. I am running the simulator as an Administrator. I have done a complete slow repair of all files. Did not help. I have uninstalled and reinstalled the AH-64D module. Did not help. What should I do now? Thank You for your help !
  10. This problem is with both the pilot and the CP/G keyboard settings. I can save a file and it appears to have saved. Then when I try to load it the file name is not there. It says "The file can not be found". Then if I exit the simulator and check the folder for the file it is really not there. So it was never saved. I have done a complete slow repair of all files. Did not help. I have uninstalled and reinstalled the AH-64D module. Did not help. What should I do now? Thank You for your help !
  11. I am using SimFFB version 3.2 with a MS FFB2 stick. The program is working. There are stick forces and the stick can be adjusted with the POV. I can adjust the rudder and ailerons trim. But I can not adjust the elevator trim. I can see the control wheel turning in the correct direction in the cockpit. I am adjusting trims with the keyboard. The plane is the P-51D. Thanks to all !!
  12. Thank you 312_JS for updating me on this on going problem. I think FFB is needed to  fly the Warbirds. I have tried my X56 and it is just not the same. I will continue to search to find a work around.

  13. I have a problem with my FFB 2. It works great with the P-51. All of the axis stay centered. But when I use the same settings in the Mosquito, the Y axis is off center. I can move the full Y axis and it never goes back to center. This makes it hard to trim the pitch as stick inputs make the nose bounce up and down. The X and Z axis are always centered. EDIT: The black square that shows the joystick position always returns to zero. The red dot does not. The red dot is to the left of center, on the negative part of the curve. (Curve goes down) This makes the total width of the red dot's center travel unequal. There is more on the left side.
  14. I posted this as a Mosquito problem. I think it is the same as the problem that started this thread. I have inverted the FFB axis. I know my FFB2 is working correctly too. I also have a problem with my FF2. It works great with the P-51. All of the axis stay centered. But when I use the same settings in the Mos, the Y axis is off center. I can move the full Y axis and it never goes back to center. This makes it hard to trim the pitch as stick inputs make the nose bounce up and down. The X and Z axis are always centered. EDIT: The black square that shows the joystick position always returns to zero. The red dot does not. The red dot is to the left of center, on the negative part of the curve. (Curve goes down) This makes the total width of the red dot's center travel unequal. There is more on the left side.
  15. EDIT: The black square that shows the joystick position always returns to zero. The red dot does not. The red dot is to the left of center, on the negative part of the curve. (Curve goes down) This makes the total width of the red dot's center travel unequal. There is more on the left side.
  16. I also have a problem with my FF2. It works great with the P-51. All of the axis stay centered. But when I use the same settings in the Mos, the Y axis is off center. I can move the full Y axis and it never goes back to center. This makes it hard to trim the pitch as stick inputs make the nose bounce up and down. The X and Z axis are always centered.
  17. Hi Firmek. Thank you for taking time to write me a detailed reply. I read through it and I know I'm going to have to adjust the values before I fully understand it. I was trying to adjust the FOV in SnapViews.lua and the min/max in Server.lua. I have not had time to try again. I did not know or understand the exact relationship between these values. Oh, and thanks for going the extra mile, for the DCS option. Thank you!
  18. I am adjusting FOV with line [13]--FOV in the SpapViews.lua file.  I do not see any changes in the cockpit.  The only way I have been able to adjust it is in the Server.lua file.  By changing the upper limit in line 7, gCameraViewAngleLimits.  I do not think this is the way to do it because I think it changes every aircraft.  Also, I am still adjusting the P-51 and I can not get it to work on either version.  Thanks again!

  19. I am adjusting FOV with line [13]--FOV in the SpapViews.lua file. I do not see any changes in the cockpit. The only way I have been able to adjust it is in the Server.lua file. By changing the upper limit in line 7, gCameraViewAngleLimits. I do not think this is the way to do it because I think it changes every aircraft. Also, I am still adjusting the P-51 and I can not get it to work on either version. Thanks again!
  20. Thank you very much for your prompt attention to this problem. I have not tried it yet, but I am sure it will work now. I also like the Jug and the Spit. I have a mission that forces you to start with the P-51 NA version. Then you can choose another plane. The FOV problem continued to any plane you selected. Here is a link to that mission. It has many options you can select and I enjoy flying it. Thanks again !
  21. Let me first say I have used this for a long time. It has always been very helpful and worked great. Thank you for your continued hard work keeping it updated. Since the last update I have had a problem with the FOV between two aircraft of the same type. The P-51D and the P-51D-30-NA. The FOV for the P-51D is correct, that is the way I want it to be. But the FOV in the P-51D-30-NA is to far back from the instrument panel. I think I have all the setting in SnapViews.lua and Server.lua the same for both planes. Also I am using TrackIR. The two files I attached are instant action, free flight selections. I know I probably missed something or am doing something wrong. Thank you very much for your help. johnjar johnsonjar28@yahoo.com
  22. Thank you very much everyone for your help with my problem!! I will keep trying and checking the things you wrote. Also thanks for giving me more detail. I think I understand it now.
  23. I have rotary controls assigned to each of the trims. I found that if I first adjust each trim to get straight and level flight using the keyboard; I can then make adjustments as needed using each rotary. I never had to do this for the P-51D. I guess just another difference between British and American planes. I'm still not sure it is working right, but at least it is kind of flyable. More help will be greatly appreciated!
×
×
  • Create New...