0xDEADBEEF

Wow, quite some activity since I last checked, nice to see! @propeler I wanted to check out your new firmware that works with odrive, but it seems your repository is gone again? What's the deal here? I still have my old assembly mechanically ready but I never go to finish the controller. I do have an odrive board I can just flash the firmware to, but it seems it's not available anymore?

I would really put 1 at the end. But other than that It's a very solid list. It would be marvelous to see an ED Employee specifically responsible for Mission Scripting purposes. There's so much potential to empower the users to create better content. I am 100% sure it would be fantastic return on investment for ED.

Very nice, thank you! I had no clue there was an odrive library for arduino This alone will save me hours! I had the original MS FFB Pro in the 90s, I think it's still in my basement. Can't wait to finally fly with force feedback again with a proper grip and more torque thank you guys! What a fun project!!

Would you mind sharing your code? I just finished my mechanics and am about to tackle exactly this. I was actually looking at fino, but it seems it does not really matter which library to use I'm going direct drive with hoverboard motors by the way, landed a nice deal on a used hoverboard without charger for 30€. I was lucky the seller did not check used prices on those boards, a charger would have only been 15€ on amazon ...

Ahh that is very good to know, thanks! I understand it was cheaper back in the day. That is good news for most of us, odrive is rather simple to obtain, albeit not cheap, it's still affordable ouch that's bad news, but understandable. Any news on wether there will be support for warthog-style grips? Maybe I could contribute some code for that in the future, shouldn't be too difficult. Oh and one more question, would you mind sharing your original Fusion 360 designs, alongside the step assembly? Again, thank you for the great work you've shared!

Hey @propeler! I've had some closer look at the schematics and pcb (Very nice work on the PCB by the way . I always appreciate when layouts are a piece of art and not just a bunch chaotic connections). It seems the main difference to a stock Odrive is you are not using the DRV8301 motor drivers, but instead half-bridge ICs with separate current sense amplifiers for each phase. What's the reason you are doing this instead of just measuring the total consumption of the Motor as Odrive does? The reason I'm asking is because sourcing those current sense amplifiers in the current semiconductor shortage is really hard. The only source for them I could find is aliexpress, and they are 25€ each, multiplied by 6 those suddenly become more expensive than the whole board I do happen to hav a few F405 MCUs around from repairing drone flight-controllers for friends and the half-bridge ICs are rather easy to get in comparison. I'm looking for the best solutions to proceed. Ofc if you could provide a version that works with stock odrive would be ideal (already have one of those). Or maybe substitute those ics with jellybean opamps would probably be most const effective, but for that I'd need more understanding how the circuit works. Ideal of course would be if you shared the sourcecode so we can adjust and make that build ourselves. I'm a bit late to the party so I don't know if releasing the source has been discussed or if you plan to do it or not. It would for sure be a huge contribution to the community if you did! The hardware design itself is already fantastic! We just need a way to maneuver around the semiconductor shortage

@propeler amazing work! Why are you not putting the code on github? Everything else is there, it would only help improve the project!

Realistic or not, archairpilot me can't tell, but I can tell that I am incredibly busy making sure I operate it within sane parameters, and still wonder why there is only occasional radar returns, and if I manage to track a target, the track will be long lost before any aim 120 goes active in bvr engagements, and if I make it WVR i have much higher survival chances using my eyeball mk1 ...

Same problem here as well, Radeon 5700XT

I like the freedom of picking up whatever Mission comes along your flight, but maybe it would be good to be able to select a mission and have it exlusively available for yourself, to prevent others from "looting" it ...

Hello! As per the documentation on hoggit the S_EVENT_MARK_ADDED event is supposed to contain an initator parameter. This would also be absolutely expected, as you would not be able to tell who placed the mark otherwise. It appears on my test-rig that with the current OB Version the initiator parameter is not passed along the mission (or is passed as nil, which is the same). This is the table I receive with the event: event = { ['coalition'] = 2, ['idx'] = 251658242, ['time'] = 28930, ['id'] = 25, ['text'] = '', ['groupID'] = -1, ['pos'] = { ['y'] = 522.64993671191, ['x'] = -239932.57126467, ['z'] = 734296.67458392, }, } Setup to reproduce: simple mission, add a script handler. Run in dedicated server on local machine in separate work directory. Connect as a client with standard dcs installation. Place mark. No initiator provided.

Thank you very much c0ff! Much appreciated!

Every server is different in that regard. you will have to name the server to get a definite answer.

It (wrong client id returned in server side) did happen again after the server being up for 25 hours. One weird thing I noticed was a Unit:getName() threw an error: "Unit doesn't exist", even though the line before is "if unit:isExist() then" and apparently returned true. I also notice inconsistencies with hit event. The initiator and the weapon are identical, however I cannot call getPlayerName() on the initiator, I get "attempt to call method 'getPlayerName' (a nil value)". All this started at the end of the log and the 24 hours prior. log is attached. Interesting events happen at the end around 20:00. dcs_log.rar

Unfortunately this bug is still unfixed. Please let us know if we can do anything to help you reproduce the issue. I (we) can run any script you want on the server to collect information that helps to reproduce. This is a serious issue for many servers, please let us help! Edit: disregard, sorry! I got relayed incomplete information. It seems the scoreboard is still recording kills for others, but the kill event on the serverside script now returns the correct client id! I'll have a closer look when i find time.