Jump to content

mkiii

Members
  • Posts

    679
  • Joined

  • Last visited

Everything posted by mkiii

  1. It's a good job we don't have simulated smells in the sim. Have you ever caught a whiff of what a seagull stinks like after it has splattered itself on or in a jet fighter? Whoa.... hot fishy chicken! : /
  2. If you went as far as deleting the Keystrokes associated with it, and all other inputs then it is a mystery why it might still be doing it. You might get something like this problem if you had an Autostart procedure that was accidebntally being triggered (canopy at least) but the SU25T doesn't have one. I certainly get similar problems in the Mig21 when I flip the wrong switch. Have you checked your Modifiers to make sure something there is not set up incorrectly... sending an errant keystroke or somesuch? Do you have any 3rd party Mods that might be doing weird stuff? Are you using any scripted controllers such as Warthog Target SW or Saitek Profile SW? They can do odd things if the wrong commands are being sent. Especially if your controllers have changed order in the USB list. Have you tried Repair DCS from the start menu? Last resort, delete the SU25t and reinstall it?
  3. Thanks for the hard work, but I'm having a litle problem with any modified Kneeboard that I try to use. No Matter what settings I have, including Lite mode, the User Mark point does not appear in any Kneeboard positioned by KneeboardBuilder. Ones that have not been setup in KneeboardBuilder (and have the kneeboard in its original position off to the right) do show the User Markpoints. Waypoints and lines show up correctly, and use any custom colours, but not user marks, I tried different colours and varying Alpha settings to no avail.
  4. Set everything up in the GUI so the second monitor is included (for width and aspect ratio), so the figure there would be 3540, and 3.27777777 for the aspect. Not sure why you have to choose the wrong res in the gui. DCS Should pick up the correct width of both monitors combined as per your GFX setup??? You can try manually entering the correct figure into saved Games\Config\options.lua Look under["graphics"] ={ .... ["width"] = nnnnn Use a copy of the Single screen setup with the additions shown above. something like this in Monitorsetup _ = function(p) return p; end; name = _('test'); Description = '2 screens as 1 viewport plus smaller Monitor on Right' Viewports = { Center = { x = 0; y = 0; width = 1920; -- note: width of main screen - not full width of 2 height = 1080; -- 3d world will only display in this area. viewDx = 0; -- Options.lua via the gui option settings uses 3540 as the screen width. viewDy = 0; aspect = 1.77777777777; } } -- You might want this too. Just alter sizes and placement to suit LEFT_MFCD = -- Built-in so no setup other than this required { x = 1921; y = 0; width = 536; height = 536; } RIGHT_MFCD = -- Built-in { x = 2163; y = 0; width = 536; height = 536; } -- as mentioned above, keeps gui on left screen. GUI = { x = 0; y = 0; width = 1920; height = 1080; } UIMainView = GUI This type of setup works OK for me at least. I have 3 monitors set up as 1 viewport on the Left, and a smaller monitor for MFDs on the right. My numbers are different, but the basic setup is identical, using the default single monitor config as a base.
  5. You might want to check this out :- https://forums.eagle.ru/showthread.php?t=129341 If your folders are named correctly, then it should work. I just tried it with a bunch of checklists in jpg format for the spitfire MkIX downloaded from User Files here, & it worked OK doing it as you described in the 1st post. @Andy1966: Do .pdf files work anyway? I tried adding one and it certainly doesn't appear. Don't you need to conver it to images before you can use it?
  6. Perhaps it is just something as simple as having now bought the spit, that my Dora is jealous? Or more likely, my muscle memory is confused...
  7. If you are using multiple monitors as one desktop, try this:- I am using 3x1920x1080 monitors as one desktop/screen (Actually, I am using this setup + one extra monitor to the right, but that just entails adding the width of that to these settings in the GUI). _ = function(p) return p; end; name = _('3inone'); -- call it whatever the file is named Description = '3 screens as 1 viewport' -- for info only Viewports = { Center = { x = 0; y = 0; width = 5760; -- note: width of the 3 screens height = 1080; -- 3d world will only display in this area viewDx = 0; -- Options.lua via the gui option settings uses 5760 as the screen width. If any additional - non 3d world monitors are used for MFDs etc, the GUI will use THAT width viewDy = 0; aspect = 5.33333333333333; -- 5760 / 1080 } } -- .... MFD STUFF HERE -- .... ........................ GUI = { x = 1920; -- puts gui on centre monitor -- x = screen.width / 3; y = 0; width = 1920; -- width = screen.width / 3; height = 1080; } UIMainView = GUI -- force GUI to appear in the above screen.
  8. Windsocks (and smoke plumes) Point south when a north wind blows, but no one finds that confusing when the tower tells you the wind direction is 0 degrees, so just mentally call the arrow in the editor a windsock and it is fixed. No need to change it. ;)
  9. Slightly off topic, because short of rewriting a lot of code (the comms gui seems to operate via its own scripts rather than normal keyboard commands), I can't see any obvious way, but... am I alone in only just realising that you can actually click on the Comms items to select them? All this time, I have been messing with the keyboard (which I normall have slid under my desk), when I could have just used my mouse. ;/
  10. Thanks for the excellent guide Chuck. Just a slight quibble with Part-5 Taxi procedure: "During taxi, keep the control stick pulled completely AFT to ensure the tailwheel remains straight" Shouldn't that read "to ensure the tailwheel stays on the ground"? Unless there is some sort of tailwheel locking (other than the natural tendency of a trailing caster to run straight) that I am unaware of, which is not impossible of course ;) And in "Takeoff", item number 10 mentions braking to stop the wheels spinning (as in the FW 190D). Spitfire Pilots notes do not mention this (MkI,II or IX). Is it necessary?
  11. Ah.. Those lights. Sorry. Confirmed. I can't see them with my arrangement. Forgot they were there ;)
  12. ... unless you have a really good aim ;)
  13. What version of DCS World? [EDIT] I don't see it in updated 1.5.5.5 stable. Counters are set & counting down correctly during a quickstart mission, and are reset correctly after refuel & rearm. Bear in mind that the ammo counters only count down from what they were set to, & lower after each round is fired. They don't show the actual amount of ammo loaded. If you refill the ammo but the counters are not set to the correct amount, then the guns still work, but the counters might show empty.
  14. Since the update to 1.5.5.5 has anyone else noticed that the Dora is now somewhat harder to land (& take off), or am I just out of practice? [bUMP] So No One has noticed any changes since 5.5.5.5?
  15. which version are you running? Have you a: checked the button assignment is correct, and not duplicated? b: tried it during normal flight? You might already be dead.
  16. Oh, I never thought of moving my head or removing the pilot. I'm such a dolt ;)
  17. Where does that info (regarding Smart Scaling) come from? Everyone is talking about it, but can someone point to the official word on this? On the subject of Model enlargement, smoke from burning targets now seems to be much smaller than it was prior to 1.55. If I burn a tank now, the smoke plume is barely visible when I have started to turn back towards the target. it seems more like the amount of smoke you might get from a coal fire, not a burning vehicle.
  18. Well yes, perhaps, if you were flying without any sort of radio gear & couldnt triangulate your position idoing it the old fashioned way by looking at features on the ground and comparing them to the map you have in front of you.
  19. On my setup, which I pretty much left alone until 1.55 came out, it does not seem to be working at all. Now, I see no difference between Low or High settings, and even trying to see static targets on a range, where I know their locations seems to be very tricky. For example, before 1.55, flying the Mirage 200 Caucuses Ground Attack Mission, with Enlargement set to low, I could see that Civ traffic in the distance was enlarged, now that effect is missing.
  20. Considering that the SC50 has only 1/4 of the explosive that a Mk82 contains, and the end terrace wall was pretty much taken out, I suspect that bomb 2 would have taken out that building with blast damage alone. A terraced house I once lived in had bomb damage caused by luftwaffe bombs dropped 2 streets away (about 250m). According to an old lady living across the road, who was there when it happened said it was like an earthquake.
  21. I just wish I could get the little fella to move his hand so I can see the trim indicator.
  22. It might be my setup, but I did read an earlier tip to correct only with right rudder, so I start the run with stick back and a little right rudder, but releasing, and adding it to correct drift, like Grundar, relaxing it once the tail is up. The key for me at least was to add a little nose down trim before rolling, not leaving it at 0 degrees as per manual. The most important thing for me is to relax the back stick at the correct time, giving it right aileron to correct any tendancy to roll, and even a little forward stick if the nose tries to rise too quickly. Still not perfect but getting there.
  23. Just in case anyone wants to edit the texture files to make the white indicator more visible (it is v blurry on original texture), Here is where it is on the texture. This just happens to be the US one I experimented on. The key is the 04 in the file name. There are 2 wing textures , the indicator is on the starboard wing map.
  24. @rrhode: The gear indicators on the wings have a white portion where it meets the wing, if not visible, then the gear is not fully down or damaged. It is probably only 1cm or so deep, so may not be very visible on some setups. @dallas48: It is for an A8 rather than a D9. Sorry, no matter what I do, it appears here as a document. (you should be able to dl from the pdf in the post). If you want to go to the original page, it is here http://www.lexpev.nl/manuals/index.html This link shows details of the gear. There is no down lock, just the pressure of a smallish spring, and the gearing of the electric motor itself. http://www.clubhyper.com/reference/fw190landinggear_1.htm
  25. YUP. Working on Puma and Wessex in the late 70s in the RAF, we certainly had, and used rappel ropes for the standard infantry squaddies to monkey down en mass.
×
×
  • Create New...