Jump to content

Griffon345

Members
  • Posts

    74
  • Joined

  • Last visited

Everything posted by Griffon345

  1. Really enjoying this little helo and am trying my hand at skinning it for a South African and UK bush scheme. I use GIMP and when importing the skin psd files the bump mapping and shading of panels and fasteners etc are missing. If anyone has the time and are willing I'd appreciate a quick (if there is such a thing) steer on how to show these from the template in the user files. Failing this, if it's that's a huge mission would anyone be willing to share copies of the virgin files in xcf format as many have obviously managed to have the above shown correctly. Including the SA342_Camou_ADT_8.
  2. Still no reply from ED. Hopefully next patch will help?
  3. I thought I'd broken something with adding modded trees but on switching back and forth between stock and mod I have the same problem mentioned. It seems random, even on DCS restart, although I've only used the trigger without a condition. I can confirm that the more one edits the worse the problem and DorianR666 finding that the removal remains in editor, additively across missions. I'll set it to option 3 mentioned with a timed condition and hope for the best.
  4. I've had the same issue but with the openbeta version of DCS. Model viewer opens and works until I try to load a model or open preferences. It then crashes and closes. I've removed mods, cleaned and repaired, deleted folders and saved game directory. Nothing works. Run out of ideas. Log file attached. Update: Reinstalled from scratch with same result. Anyone? (Updated log file attached) model_viewer2.log
  5. Thanks Tom. Looks like it was due to Ns430 modules bindings I had set competing for the button press. I moved them to other unused buttons and it worked. Sorted. Looking into deleting all keybindings I don't use to prevent conflicts. Sent from my SM-G975F using Tapatalk
  6. My solution is to save all my bindings to their own file eg: SLR_MI8MTV_JOYSTICK etc. After an update I first confirm there are no new bindings or controls. If so, upload each file as appropriate and fly. OVGME I use for custom controls (toggles, 2 position switches, etc) until ED include 'press' and 'release' modifiers and make my year. Sent from my SM-G975F using Tapatalk
  7. I'll chime in. Previous to the last 2 updates it worked fine. Now functionality lost. Removed all mouse, repair and clean but still no ops. Tested 4x modules. Sent from my SM-G975F using Tapatalk
  8. Question answered already! Cannot wait. Sent from my SM-G975F using Tapatalk
  9. How about including 'press' and 'release' as modifiers for all setups. This would satisfy many threads I have researched as well as rounding out perfect native support for every controller available (sic). I admit I have no idea how easy this is to do. Sent from my SM-G975F using Tapatalk
  10. Great steer thanks! But it would be nice if paralleled by official sources. Resources not available? I'd have to say I'd prefer updates towards a complete F/A18 product than an official manual. Many talented individuals taking care of the latter and open source docs to suppliment. Sent from my SM-G975F using Tapatalk
  11. I have a modified server.lua file in my savegames folder to gate the maximum FOV zoom out to 85-97 depending on the aircraft. I've done this as I use the right brake pedal as a FOV zoom slider and would get full (120) zoom out when the pedal is not pressed if not modded. This is obviously not going to work as the view is way too zoomed out and fish-eyed to fly with. The mod works like a charm in SP but not in multiplayer. Am I correct in saying the modded server.lua is completely ignored in MP mode and if so, anyone know of a solution to force max FOV zoom to around 90 in MP?
  12. When I map the PCA (or anything else) to my 3rd Cougar MFD buttons, some key-presses register in cockpit whilst others do not eg: up toggles on VTB controls work whilst down do not. Mapping these same keybinds to MFD1 and they work (except as noted by Lorthirk above, that key 5 never registers). In the binding setup screen the key-presses register as programmed. This is with or without mods. Help? i9-9900K, 32Gb, GeForce RTX2080, Samsung 850EVO and 950EVO 500Gb SSDs, TM Warthog, Saitek Pro Flight Rudder Pedals, TrackIR, X Keys XK-60 and 3x TM Cougar MFDs.
  13. Not sure this is what you're looking for but I moved mine to a 4th monitor as follows: -Open "DCS World OpenBeta\Mods\aircraft\M-2000C\Cockpit\VTB\VTB_init.lua" -Change the entry "try_find_assigned_viewport("RIGHT_MFCD")" to "try_find_assigned_viewport("M2000C_VTB")" or whatever you wish to call the viewport. -Create a monitor setup file in "[drive]:\Users\[username]\Saved Games\DCS.openbeta\Config\monitorsetup" that references this viewport and set coordinates as you need for placement. (my file attached) Entries in [] are obviously your own. and works for stable branch as well. I've exported the following viewports in this fashion: VTB, RWR, PCN, PCA_PPA, COM. Some entries required for those *_int.lua files that don't include a viewport (let me know if you need this) Hope it helps Cougar_MFDs.lua
  14. Behind the bomb carrier. Fairing? Sent from my SM-G975F using Tapatalk
  15. Good steer, thanks Parrotman!
  16. It's odd logic but this works every time. Doesn't make sense though. Can anyone confirm this is how it's design in the real jet? Sent from my SM-G975F using Tapatalk
  17. Many thanks Chuck. Life is easier with your guides. Sent from my SM-G975F using Tapatalk
  18. Cannot get correct reaction when mapping: ANTI-SKID Switch - PARKING BRAKE/ANTI-SKID, to 2 position switch on my TM Warthog throttle base. With switch in OFF in cockpit, cockpit switch will select ANTI-SKID mid position when toggled both on or off on Warthog base. With switch in PARKING BRAKE in cockpit, cockpit switch will select ANTI-SKID mid position when toggled on but not when toggled off on Warthog base. No other selection (specifically the expected PARKING BRAKE/ANTI-SKID toggle) works.
  19. This is working as advertised. Temperature affects instrument indicated altitude as all altimeters are calibrated to display accurate altitude under ISA (International Standard Atmosphere) conditions. If the temp is higher than standard the altimeter will under read, of colder, it will over read. https://www.ifalpa.org/media/2012/15atsbl02-cold-temperature-corrections.pdf It is odd that at 15 deg the altimeter reads correctly though. Standard temp is around 13 deg at that altitude for accurate altimeter indication. Is the temp setting as you have it in your test at sea level?
  20. Thank you for this! Clue as to get in to the command_defs.lua and fiddle further. If you have time to steer me to the doc with more of this info (my apologies if it's in the manual) I'd be much obliged.
  21. Excellent and good to know it's not my side. Cheers for the update.
  22. Yes please. This would make native keybinding nearly complete.
  23. I have the same issue with the lighting on the models extremely bright as if lit up by a searchlight. It works otherwise...
  24. In the same vein: both Warthog throttle and joystick show in Devices and Printers and work as advertised. However when using the Target Device Analyzer: Without a script running, only the Throttle shows. With a script running no devices show although the Virtual Game Controller shows correctly in Devices and Printers and Game Controller settings. Short version: the system works (buttons, axis etc) but device analyzer does not display them correctly. Tried all I can think of but no change... Any other ideas?
×
×
  • Create New...