Krinje

I can highly recommend adding transducers (like the buttkicker) to your chair I just finished a project and added 4 TT25-8 transducer pucks to an office style chair. That setup is 80 watts, and its fantastic and not just for DCS either! I'm quite sure I'll soon be adding a system to the living room couch for movies and TV. Next to TIR this was the most immersive addition I've made yet.

I'm embarking on a design experiment and to start I need to define some goals for the project to see what is reasonably achievable within a budget (tbd). Adding a length extension and force feedback to an X55 is the goal of the project. Specifically I'm looking for information on real examples of stick force for several types of aircraft. This is so I can get a good idea of what it would take to replicate reality vs what is practical for design, space and budget. I need examples of peak forces/resistance for: Warbirds, direct cable driven surfaces. Hydraulically assisted controls. Fly-by-wire feedback. Rotarcraft direct and hydraulic. Any units of measurement are appreciated! Also, Does anyone happen to have a number in regards to realistic cyclic lengths? Could really be any helicopter, I'm just looking for a ballpark. Ideally a Gazelle or KA-50, but anything will do. Thanks for your help!

M36 x 1.5 is the closest standard, and most likely thread. (measured by myself) it is absolutely 1.5 pitch, very close diameters to a nominal M36. Something like one of these is the spring loaded pin: https://www.digikey.com/product-search/en/connectors-interconnects/contacts-spring-loaded-and-pressure/1442508?FV=1140050%2Cfff40016%2Cfff802cc&mnonly=0&newproducts=0&ColumnSort=1000011&page=1&stock=0&pbfree=0&rohs=0&k=pogo+pins&quantity=1&ptm=0&fid=0&pageSize=25&pkeyword=pogo+pins I don't know the layout or size of the pins, but I was also investigating.

Has anyone figured out how to turn on the in-cockpit rendering? I commented out all 4 of the rendering purposes in various combinations, but it appears they both use inside cockpit. Its kind of a bummer, I'd like to be able to save some framerate. (this is in the init.lua) -- The code below is used for rendering When you use viewports comments are same as above for rendering purposes = {render_purpose.HUD_ONLY_VIEW, --render_purpose.GENERAL, --Uncoment this line by removing the "--" to render in 3D cockpit. render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always -- End of rendering configuration render_target_always = true also; my setup. x = 20 is approximately correct, the -6 is exactly right for the offsets to get it flush with the edges of the screen. (these extra offsets seem to change with TV w/h) Normally the taskbar is not in the way, that was because DCS intercepts my keybind for Puush (a ss/upload program). This is from the Camera+GTV.lua SA342_TV = { x = 20; y = 1080-360-6; width = 450; height = 360; }

Excellent. Because the NADIR displays LatLong as a 7 segment style display and the TV has 3 numerical and important pieces of information. I think that second tip will prove very useful. As it stands: --Version 0.2 local host = "localhost" local port = "8080" local socket = require("socket") local c = socket.try(socket.connect(host, port)) local PrevExport = {} PrevExport.LuaExportStart = LuaExportStart PrevExport.LuaExportStop = LuaExportStop PrevExport.LuaExportNextFrame = LuaExportNextFrame PrevExport.LuaExportAfterNextFrame = LuaExportAfterNextFrame PrevExport.LuaExportActivityNextEvent = LuaExportActivityNextEvent function LuaExportStart() --Start tcp Socket package.path = package.path..";.\\LuaSocket\\?.lua" package.cpath = package.cpath..";.\\LuaSocket\\?.dll" --socket = require("socket") --c = socket.try(socket.connect(host, port)) c:setoption("tcp-nodelay", true) socket.try(c:send("Gazelle Calc Export: STARTING, \n")) if PrevExport.LuaExportStart then PrevExport.LuaExportStart() end end function LuaExportNextFrame() --Nothing if PrevExport.LuaExportNextFrame then PrevExport.LuaExportNextFrame() end end function LuaExportAfterNextFrame() --Nothing if PrevExport.LuaExportAfterNextFrame then PrevExport.LuaExportAfterNextFrame() end end function LuaExportActivityNextEvent(tCurrent) local tNext = tCurrent + 0.5 --local gazelleM = --Gazelles ID number --local gazelleMin = --local gazelleL = local craft = LoGetPlayerPlaneId() --[[ if craft == gazelleM or gazelleMin or gazelleL then --GazelleID number local altBar = LoGetAltitudeAboveSeaLevel() local nadirLatLong = --I don't know what these are yet, I need to do some diging. local bearing = local tvBearing = local laseRange = socket.try(c:send(string.format("craft = %d, altBar = %d, nadirLatLong = %d, bearing = %d, tvBearing = %d, laseRange = %d"))) --I don't know what types most of these will be int(%d) place holders. end ]]-- socket.try(c:send(string.format("craft = %d, \n", craft))) if PrevExport.LuaExportActivityNextEvent then PrevExport.LuaExportActivityNextEvent(tCurrent) end return tNext end function LuaExportStop() --Close Socket socket.try(c:send("Gazelle Calc Export: STOPPING, \n")) c:close() if PrevExport.LuaExportStop then PrevExport.LuaExportStop() end end I honestly don't know *why* I'm doing the callbacks, just that they seem to work and you said to do them and I couldn't quite figure out why. I'm mostly done head scratching for the day. I'm trying to bite this off one piece at a time. For now, connecting once is acceptable. figured out my problem with string.format, I miss understood how it functioned from the examples in export.lua and it is now working fine. I am now seeing the KA-50 as 16779520 in SocketTest. Again thank you very much for your help so far.

Thank you for the excellent reply. I've written a simple calculator in Java for the calculation of Lat/Long of a target via bearing and distance provided by the gazelle's optics and ranging laser. I'm looking to automate much of the data entry by getting NADIR's (your position) lat/long, hopefully the camera's bearing and lased distances etc... The if than statement is to filter out non-gazelle aircraft and avoid unnecessary work/possessing because I don't know how much or how negligible this is for DCS to run. The gazelle currently has 3 airframes which I assume all have different IDs. Using a program called SocketTest, I confirmed before I saw your post the connection attempt issue. I did create the socket, and close the socket (yay!) but even when commented down to just the PlaneID and subsequent send I did not receive data. (wrong type? %d?) Thank you very much for pointing me to some good source. I think I'm going to take a look at the both examples, and attempt the UDP. Is this a good example of global table? (from Simple Radio) #Edit: Never mind that, I figured out what you meant.

Even without a FFB stick the magnetic trim is a wonderful tool. Their really isn't a reason not to use it. It's easy to trim out the Heli in forward flight better than the autopilots, but you can also trim in a graceful turn or orbit. It practically flies itself. Generally speaking whenever I am changing flight profile I simply (magnetic) trim into what I want.

This is my first time attempting an export (or any udp/tcp connection), I think I understand what is going on. I followed the export.lua's example. I'm unable to test at the moment (partly being unfinished) but mostly I do not have a listener written yet. The listener will be part of a Java application. I'm wondering if I'm barking up the correct tree(s) here. If I continue working on what I've got will I get the results I expect? Any sage advice is welcome, Thanks. --Start Socket package.path = package.path..";.\\LuaSocket\\?.lua" package.cpath = package.cpath..";.\\LuaSocket\\?.dll" socket = require("socket") host = "localhost" port = "8080" c = socket.try(socket.connect(host, port)) c:setoption("tcp-nodelay", true) end --function LuaExportNextFrame() --Nothing --end --function LuaExportAfterNextFrame() --Nothing --end function LuaExportActivityNextEvent(t) local tNext = t local gazelleM = --Gazelles ID number local gazelleMin = local gazelleL = local craft = LoGetPlayerPlaneId() if craft == gazelleM or gazelleMin or gazelleL then --GazelleID number local altBar = LoGetAltitudeAboveSeaLevel() local nadirLatLong = --I don't know what these are yet, I need to do some diging. local bearing = local tvBearing = local laseRange = socket.try(c:send(string.format("craft = %d, altBar = %d, nadirLatLong = %d, bearing = %d, tvBearing = %d, laseRange = %d"))) --I don't know what types most of these will be int(%d) place holders. end tNext = tNext + 0.5 --repeat every 1/2 second return tNext end function LuaExportStop() --Close Socket socket.try(c:send("quit")) c:close() end

Well done, looks great!

I'm 100% ignorant here, is or will there be an option to turn off the composit render? I would imagine that would increase performance at least somewhat. It's a very good feature for streaming but unimportant for most other things.

Teensy 3.1 It's a different chipset w/ the Arduino bootloader built in. Same easy code and libraries in a smaller more powerful package with additonal features (the uc is a cortexM4) Over kill for switches but the now 3.2 is only 20usd and the LC is around 10. Much more reasonable than 'real' Arduinos.

The Pi is fixed as a USB master and there is no easy way to make it a device. It also has comparatively limited I/O and waaaaaay more possessing than required. I'd recommend looking at the Teensy 3.2 or LC they are programmed just like an Arduino, are more powerful and cost much less. For lots of buttons and switches I'd also recommend a couple port expanders (MCP23017 MCP23008 ) they talk to the uc over i2c serial and act like (16 or 8 ) extra pins. Check adafruit they have a library for these two chips! My Panel http://I.imgur.com/JQCgCx5.jpg

I don't think his point is wrong, but MP is just as bad a reason to not have DFCS as it is to have DFCS, why would you let multiplayer dictate the implementation(s) of the aircraft? And in his own words; Don't you love the F14s with DFCS? Should you not embrace them too 'true cat lover' ? Related: I don't like the Bearcat :music_whistling:

Because a poll is going to distract Devs? You(anti-poll-posters) are also talking about a poll that was setup LAST YEAR April. None of what you are saying about the F14, F4U or Viggen existed as far as we knew and it was a good time to ask; hey, whats next? we'd love to see some parity in DCS and you did an amazing job with the mig.

Its the most ass backwards system of DRM I've ever seen and it doesn't even accomplish what it sets out to do at the raw expense of the end user. 10 keys is simultaneously far too many to stop the exchange of modules between people and far too few for a frequent user (and the apparent false-positives). It doesn't do its job, and it (as this thread's existence is proof) annoys users. Do you need DRM? yes. Is this the answer? Its the second to worst I've ever seen behind 'you must always be connected to our server at all times'

I'm a little behind on the clues, and 150 pages is quite a bit to chew, does anyone have a summery of clues?