Jump to content

No1sonuk

Members
  • Posts

    1601
  • Joined

  • Last visited

Everything posted by No1sonuk

  1. Then I've gone as far as I can I'm afraid. You should try the Flightpanels bug reporting on Github and/or Discord.
  2. Additional info in case it helps: Using a DCS-BIOS connected switch allows selection of up (open) and centre (off/stop), but not down (close).
  3. Looks like you didn't notice the subtle difference I made in the dial code. "if ( valueDial_1() == 2) {" becomes "if ( valueDial_1 == 2) {" - remove "()" after valueDial_1. You might also need an extra } at the end - my snippet was intended as an example of the beginning of the setDials function. If you stop it there, you'll need to make sure there are the correct number of }.
  4. Ah, OK. So if the expected DCS-BIOS messages are being sent, it might be the control reference messages to DCS conversions themselves are wrong. That might be a DCS_BIOS script coding issue, and I don't know it works. Which version of DCS-BIOS are you using?
  5. It's possible it might be the port reading that is the issue. Also, the switch wiring combinations are odd. I'd have thought they'd be some form of binary coded decimal or somesuch. Do you have a part number for a switch?
  6. The returned variables from your port reads (valueDial_1, etc) are unique, so you could make them global and reduce the read cycles - each of your "if" statements in setDials reads the port. You could read the port once, convert the input combination to a number, then compare the global variable to the value from DCS and send the correction if it's different. e.g. Assign global variables: int valueDial_1; int valueDial_2; int valueDial_3; int valueDial_4; int valueDial_5; Then inputDial_1 becomes: // JADRO 1MHZ Knob////////////////////// void inputDial_1() { int valueDial = PINC; // temporary int for port conversion if (valueDial == B00010110) { valueDial_1 = 2; // Set the global variable } if (valueDial == B00001100) { valueDial_1 = 3; } if (valueDial == B00010100) { valueDial_1 = 4; } if (valueDial == B00000110) { valueDial_1 = 5; } if (valueDial == B00001010) { valueDial_1 = 6; } if (valueDial == B00000011) { valueDial_1 = 7; } if (valueDial == B00000101) { valueDial_1 = 8; } if (valueDial == B00010001) { valueDial_1 = 9; } if (valueDial == B00010010) { valueDial_1 = 10; } } ////////END OF 1MHZ knob Set the other dial globals in the same way. Then the beginning of setDials becomes this: void setDials(int timer){ inputDial_1(); // Read the dials inputDial_2(); inputDial_3(); inputDial_4(); inputDial_5(); // Check and adjust selector dial 1MHZ if (DCS_valueDial_1 != valueDial_1) { // use the global variables if ( valueDial_1 == 2) { sendDcsBiosMessage("PLT_JADRO_1M", "2"); } if ( valueDial_1 == 3) { sendDcsBiosMessage("PLT_JADRO_1M", "3"); } if ( valueDial_1 == 4) { sendDcsBiosMessage("PLT_JADRO_1M", "4"); } if ( valueDial_1 ==5) { sendDcsBiosMessage("PLT_JADRO_1M", "5"); } if ( valueDial_1 == 6) { sendDcsBiosMessage("PLT_JADRO_1M", "6"); } if ( valueDial_1 == 7) { sendDcsBiosMessage("PLT_JADRO_1M", "7"); } if ( valueDial_1 == 8) { sendDcsBiosMessage("PLT_JADRO_1M", "8"); } if ( valueDial_1 == 9) { sendDcsBiosMessage("PLT_JADRO_1M", "9"); } if ( valueDial_1 == 10) { sendDcsBiosMessage("PLT_JADRO_1M", "10"); } // And so on... Primarily, only programme one of the dials first. Get that working, then move onto the next. There's no point putting all five dials' code in if you have to keep changing it to get it going. Do one. Fix it, then write the others.
  7. Have you matched the text case? Sometimes in coding, "HY4" is not the same as "hy4".
  8. Which aircraft? The Air Corps library has a LOT of high-res drawings for older propeller aircraft. It's a subscription site, and downloading full high-res copies isn't free, but you can zoom and screen grab. https://app.aircorpslibrary.com/ They have the landing gear geometry and component mechanical drawings for the aircraft I'm working on, as well as instrument panels, etc. If you let me know what you're after, I can have a look and tell you if it's there.
  9. The links on the first post in this thread. They're labelled wrong, though. The one marked guide is the sample files zip, and the one marked sample files is the guide pdf.
  10. "Physical material" didn't work for me. I had to set it to "Standard(legacy)".
  11. @Kenpilot: If you can connect your devices individually to different ports, it's likely to be a power issue. If you're running through a USB hub, make sure it's powered externally from the computer. You might be putting too much strain on the USB port power supply. Are all the devices the same type? e.g. all Nanos or all Unos, etc. If they are, try one of a different type and see if you can get two to connect. Even a different source of the same device might help. If that works, you have a USB ID conflict that will be hard, if not impossible, to fix.
  12. It'll be Hub if he's talking about autoconnect. Flightpanels fork doesn't have that.
  13. My undercarriage is raising and lowering too fast. How do I change the animation duration? I tried copying the appropriate parts of the "mechanimation" section of the Mosquito lua, but it had no effect.
  14. How do I do arg based visibility animation in 3DS Max? I have args 407 and 408 running my two props properly, but I need to switch the blades from normal for the startup range of -100 to 0, over to blurred blades for 0 to 100. How is that done?
  15. A few years late, but someone may find it useful in the future. I took the beginners' guide F-104T lua file and modified it from a single turbojet to twin radials for my mod. The engine data came from the Yak lua (search for "engine" in the flight model data area), and I referred to the Mosquito for the twin engine parts (engines_count and engines_nozzles sections). The Mosquito also had "engine_name" which I have yet to play with. I assume that ties up with the sound information in another thread.
  16. Not sure if it's common knowledge, but arg based position controllers work for animation, too.
  17. LOL Let me know how it works out for you.
  18. It should look like the photo above with the powerpack and servo. Have you done a simple I2C test with the display to make sure it's OK?
  19. How do I alter the beginners guide example from a single turbine engine to twin radials using, for example, the Wright Cyclone sounds? Edit: Found the engine type and name parameters for the lua by referring to the YAK and Mosquito luas.
  20. Thanks! The material was exactly the problem. AND I now have working model viewer, too.
  21. (Duplicate from the EDM tools thread) After installing the older plugin from the other thread, it compiled without the bounding box, but I still can't get my simple model to appear in-game, and can't get the modelviewer to work. Attached is the simple box I'm trying to get to show up before I do anything more complex. It appears in the mission editor selection, but no visible model there or in-game. DCS_mod_test.zip
  22. Thanks for the plugin. It exported without the bounding box, but I still can't get my simple model to appear in-game, and can't get the modelviewer to work. Attached is the simple box I'm trying to get to show up before I do anything more complex. It appears in the mission editor selection, but no visible model there or in-game. DCS_mod_test.zip
  23. Looks like it doesn't work right for 3dsmax 2022 either.
  24. OK. I'm at the point of fighting with incomplete 2/3 year-old information and up to date tools that don't behave in the explained manner (e.g. the bounding box error, and multiple model viewer errors). Plan B is switching to Blender, which from memory 20 years ago is a PITA to use, but there's more recent info for DCS.
×
×
  • Create New...