BrassEm

NO FIX - RELEASE OPEN BETA: 2.5.6.57264 Expect your motion rig to shake violently on shuttle hook up. Timeline is in Seconds. http://www.brass-em.com/portal/g-seat-ii f18 Syria 20201109 Jumpy.trk dcs Jumpy 20201109.log

Motion on Super Carrier has been vastly improved to 2.5.6.55960. Unfortunately the bizarre runaway shudder is still there when the alignment algorithm goes into hunting lining up the launch bar/aircraft over the shuttle. This time I have a .trk!!!!! Apologies for the shagging around in the track. (Was testing out my new wing folding key assignments and was NOT expecting the runaway.) Obviously the problem occurs right at the end of the track with the cat lineup. Pitch (green) spikes when braking has been applied. (Good!) The braking prior to moving into launch line up shows that surge has gone into oscillation but died off. (Wasnt noticed in seat.) Sway (orange) looked as though it might also go into oscillation in the lead up to the shuttle coupling. Surge (red) breaks into oscillation when the bar goes over the shuttle. User3 (blue) is just an amplification of Surge f18 Syria 20201025.trk dcs Jumpy.log

OpenBeta TACAN problems noticed after 2.5.6.55960 Installation had repair run. Gulf map; Ground TACAN works (47X) Air to Air TACAN works (1X) SuperCarrier TACAN does not work (71X) Syria map; Solitary Ground TACAN does not work (21X) Air to Air TACAN works (1X) SuperCarrier TACAN does not work (71X) F-18C Gulf 20201024a Air Start TACAN Nav Test.miz F-18C Syria 20201020b Air Start Nav Test.miz f18 Syria 20201024 No Carrier TACAN.trk f18 Gulf 20201024 No Carrier TACAN.trk dcs.log dcsold.log

The best foams are used in car seats, they are usually colour coded so you want the Salmon very high density foam. You will have to shop it from an industrial supplier though. But well worth the effort. It is dense enought that it can be sculpted with a fine wire bristle brush (from memory), but extremely messy when doing so. I got a 20mm thick sheet to layer for the comfort I was looking for. For a seat base I've used 60mm. Could go 80 for extreme duration comfort. From my old notes; FOAMS http://www.foamsuppliers.com.au/ Pink Polyurethane foams. Pink HR36-110CM5 110 +-15 50 Salmon HR36-200CM5 200 +-30 45 Resilience 45% or higher Comfort factor 2.0 110 newtons 32Kg/m3 Used HR38-200 foam. Cut in segments and glued together. 3M Super 77 Spray Adhesive. Bond-it Contact Adhesive (soft surface).

Fantastic work! Adaptable to other cockpit layouts in principle I'm sure.

I am extremely pleased to say that after about 20 or so shots and traps with Super Carrier this afternoon, that the motion is now so very well behaved. No more breaking into extreme oscillations while hooking up the puck on the deck, or shuddering around while moving around the deck. All working as it should. I even went way off line-up for the cat puck, and was smoothly glided into correct position without grief. Un-hooking the arresting wire worked well without excessive shudder too. To top it off I went feet dry and took in some of the absolutely magnificent scenery that is the Syrian Map. Many thanks to the ED team for their continued efforts. So very happy.

WOW! I can appreciate the time and effort (many repetitive iterations to see what works and what doesn't) to get a great result! Nice to see her looking half decent in game. Thanks for the heads up.

There is an intermittent problem with Super Carrier launch motion output. While the motion is now so superior to the old carrier, this problem does happen occassionally and is a real deal breaker, literally!!! I have only tested with the F-18C so cannot confirm other aircraft yet. See my website for my motion rig details. www.brass-em.com When the launch bar is going over the catapult shuttle there is some large motion surges which I assume is normal. However once the bar has dropped over the shuttle and after brakes have been applied the motion is still there in a continous hunting oscillation which cannot be stopped. (Esc key and start the mission again!!!!) The normal catapult surge is around 2.5 Starting on the catapult and launching, after several traps and launches the oscillation hit. A close up of the oscillations when they start... Hopefully we will see this addressed in a change log soon. No carrier ops for me until then. (Track and Log files too large to upload even zipped.) .

I feel your pain Helles Belle, That is as good as it gets at the moment. What looks good in modelviewer2 doesn't carry over to the sim. It will happen eventually though.

So no-one has got any code working with head shake?

I hope it wasn't BPPV :O

Found this buried in some ED code. Anyone had any joy with Head Shake output? --/* --shake level amplitude for head simulation , --prototype for ed_fm_get_shake_amplitude --*/ --typedef double (*PFN_GET_SHAKE_AMPLITUDE) (); -- From wHumanCustomPhysicsAPI.h --Pointer to function of force source in body axis --x,y,z - force components in body coordinate system --pos_x,pos_y,pos_z - position of force source in body coordinate system --body coordinate system system is always X - positive forward , -- Y - positive up, -- Z - positive to right

Just saw you post. Have you resolved the issue? I am slowly going through setting up each module for motion. I can bring the JF-17 forward in the list to do. EDIT: Can confirm there is motion on the standard outputs on 2.5.6

Am seeing this as well. No clue how to fix it.

Would it be possible to create a forum section to discuss motion specific aspects of DCS in "Input and Output"? Any gems of export.lua code or observatons are lost in the forum noise. With more motion platforms coming online people will be wanting to get the very best out of DCS. After all, motion is what VR is to flat screen monitors. Sure there are dedicated forums sections for DCS on other motion hardware sites but this is DCS, and I am sure ED won't be looking at those sites for a heads up on the state of play with motion and their software. Thanks,

Does this work any more? I've reactivated the command in export.lua and it must return a null as I cannot output the local slipball variable. It now causes a general dcs.log error for the main function. F-14 and F-15 tested. Triple checked syntax. 2020-02-23 04:49:35.463 ERROR Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Users\Dave\Saved Games\DCS.openbeta\Scripts\Export.lua"]:277: attempt to call global 'my_send' (a nil value) stack traceback: [C]: in function 'my_send' [string "C:\Users\Dave\Saved Games\DCS.openbeta\Scripts\Export.lua"]:277: in function 'AfterNextFrame' [string "C:\Users\Dave\Saved Games\DCS.openbeta\Scripts\Export.lua"]:312: in function 'OtherLuaExportAfterNextFrame' [string "C:\Users\Dave\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:205: in function <[string "C:\Users\Dave\Saved Games\DCS.openbeta\Scripts\VAICOMPRO\VAICOMPRO.export.lua"]:202>. Export.lua; local slipball = LoGetSlipBallPosition() -- (args - 0,results - 1)( -1 < result < 1) Thanks.

I've just started flying this excellent bird with an SFX-100 and g-Seat motion rig, and I am very impressed. There is one issue that most definitely needs to be addressed though. While the stall buffet looks fantastic from the pit, there is no motion output for it, at least not with my sensitivity settings. (2.5 to -1 g FSD). I get the heave and roll etc but not the shudder. It really is a breaker. Is there a way to hook into this buffet effect via .lua?

Just uploaded a video of the phenomenom. (Apologies for the loose flying.)

The SFX-100 (AASD) motion system is a proven and brilliant brute force DIY system. It does interface with DCS and has the pitch roll and heave aspects covered. But for the full effect though I feel that a g-seat on top of it is a must. Getting a good one without costing a fortune may be the problem at the moment. But know that motion is what VR is to a Monitor! :thumbup:

Thanks for letting us know so I can move on. It is a shame but hopefully there will be one as more people get into motion simulation. ;)

Thanks BIGNEWY, I am open to any testing you guys need feedback on.

G'day, I am experiencing consistent drop-outs of motion output with the F-18 while on Deck. It is always about 8 seconds into starting the mission with the F-18 on the cat ready to launch. Once launched motion returns until just after the trap and the hook is raised, and motion is lost. When I kick the tires motion returns. Note that the heave and roll of the boat is a "little" noisy. Please see the included images gSeatII_20200119a.jpg - for full flight data profile gSeatII_20200120a.png - for closeup of flight data T+4 to T+8 seconds for first motion drop-out. I have not tried any other aircraft and carrier combinations yet. I was hoping to get the F-18 working properly first. Thanks. Loss of Motion - BrassEM - DCS Bug Report.zip

[updated...] G'day majahit, Sorry but I just saw your posts now. It is good that you are getting the MCP to be seen as sending. The software is not translating the device via the keys.ini file correctly. Your device reports as FMER and the software looks up the appropriate key translation under the [FMER] section of the keys.ini file. If it found XYZ it would look under [XYZ] in the keys.ini If it's not there add it. (Although I have most devices listed on my website.) i.e. I've cut and pasted the VRInsight MCPB2 outputs under [FMER]. I am assuming they are the same as the MCP V1 (FMER) but from your example it looks like they are not. (Still looking for my MCP V1 notes.) You may have to populate the keys.ini with what you get shown with your device. [DEVICES] ;VRinsight Devices. FMER = COM3 [FMER] ; EFIS Encoders EFIMIN * = EFIMIN - = EFIMIN-- = EFIMIN + = EFIMIN++ = EFINDM * = EFINDM - = EFINDM-- = EFINDM + = EFINDM++ = EFINDR * = EFINDR - = EFINDR-- = EFINDR + = EFINDR++ = EFIBAR * = ; Pure encoder rotation. values not precalculated. EFIBAR - = ALT_SET_PRESSURE -3200 EFIBAR-- = ALT_SET_PRESSURE -32000 EFIBAR + = ALT_SET_PRESSURE +3200 EFIBAR++ = ALT_SET_PRESSURE +32000 ; EFIS Switches EFIVORL. = EFIVORL: = EFIVORR. = EFIVORR: = ; EFIS Keys EFIFPV . = EFIMTR . = EFIWX . = EFISTA . = EFIWPT . = EFIARPT. = EFIDATA. = EFIPOS . = EFITERR. = ; MCP Encoders MCPHDG * = ;Approx 11466 counts per 10 degrees = 229.3 per 0.2 degrees. MCPHDG - = HSI_HDG -229 MCPHDG-- = HSI_HDG -3640 MCPHDG + = HSI_HDG +229 MCPHDG++ = HSI_HDG +3640 MCPALT * = MCPALT - = MCPALT-- = MCPALT + = MCPALT++ = MCPVVS * = ;Approx 11466 counts per 10 degrees = 229 per 0.2 degrees. MCPVVS - = HSI_CRS -229 MCPVVS-- = HSI_CRS -3640 MCPVVS + = HSI_CRS +229 MCPVVS++ = HSI_CRS +3640 ; MCP Switches MCPAT . = MCPAT : = MCPFD . = MCPFD : = MCPAP . = MCPAP : = ; MCP Keys MCPTO . = MCPGA . = MCPCMDA. = MCPCMDC. = MCPCMDB. = MCPCWSA. = MCPCWSB. = MCPSEL . = MCPN1 . = MCPSPD . = MCPLNAV. = MCPVNAV. = MCPFLCH. = MCPHHLD. = MCPAHLD. = MCPVHLD. = MCPLOC . = MCPAPP . = ; RAD Encoders RADFRE * = RADFRE - = RADFRE-- = RADFRE + = RADFRE++ = ; RAD Keys RADCOM . = RADNAV . = RADADF . = RADDME . = RADTRAN. = RADTFR . = RADLAMP. = RADSTBY. = ; USRBTN Keys USRBTN1. = USRBTN2. = USRBTN3. = USRBTN4. = USRBTN5. = USRBTN6. = USRBTN7. = USRBTN8. = Also make sure of any spaces and full stops on the VRInsight code on the left hand side. Is it APLAT+ or APLAT +? Have you seen this link? I hope this helps you get started. If not let us know. Cheers,

Don't worry Harry², the SFX-100 is like what VR is to Flat screens. I am still in the build stage but will definitely give some feedback when it is up and running. Keep up the great work.

Thanks harry², At least there is a handle to it. Just means much more effort to get at it.