metalnwood

I got it today, this could be just a coincidence but it happened after I turned off shadows and set visibility to low. I dont remember seeing it before making those changes.

If I believe their website with regards to their resolution , fov, and how it compares to the competition I would have to say that it would be a long time until GPU's will have the power to deal with it. It's not just the fact that they say they are pushing three times the pixels. That obviously has an effect on the framerate but the much larger FOV means you are having to render a lot more scene, not just pixels. Sounds like a good piece of hardware but with some titles struggling to get framerates good for lower end spec'd vr devices I dont see how it can be good for much more than a handful of specific and optimised games/apps? Thats the short term view from me, long term is the other guys hardware will also improve as gpu's do.

No problem, it's always worth checking though. I had a zero backlash ballscrew on one machine. It had backlash, very minimal but if the dial indicator doesnt move when you jog the other direction then it's not zero. A bigger machine with rack and pinion had about 0.03mm backlash. Only other thing I can think of but the pattern doesnt look exactly right is missing steps. I suppose you could do a quick bit of gcode to make it go to 0,0 and then a couple inches away, backwards and forwards a dozen times. Set up the dial indicator at home and see after the dozen movements if the dial is still on zero. As I say the engraving has a little bit of the hallmark of it but I dont thing so. Still, if you have nothing to do, time to spare :)

What is the collet size btw? I have ER25 on mine, I realise yours will be smaller. 1/16" inches is 1.6mm, with a 40% overlap you will be there all day!

No, dont do anything by hand, that will just show you flex etc. move the machine towards the dial indicator and make sure you move it in a reasonable amount. Then go in to jog mode and set it to move 0.01mm at a time. Hmm, I see you are dealing with imperial, I thought you canadians were metric? Anyhow jog at the smallest increment and get the dial on one of the marks. Then move in the opposite direction using jog mode. You will probably have to jog a few times in the other direction before you see the indicator move. So, if you were jogging in mm at 0.01mm and it took you 5 jogs to see the indicator start to register in the other direction then your backlash is 0.05mm and you can put that in the backlash setting with backlash compensation turned on. Now, when you change direction mach 3 will turn the ballscrew enough to compensate before it tries to move the desired amount. Do it for x and y.

Your screen is a little different from mine, what version of mach3 are you running? PS, are your units set up for mm or inches when I am looking at the velocity, accel values? I was trying to see that you did have, for sure, CV off. In my version it is on that screen but not on yours. You could try turning the acceleration down a little and see what happend, you can keep velocity the same. Now, I know you said somethings were loose on your machine and you fixed that but did you do the backlash compensation to cater for anything in your ballscrew/leadscrew, whatever your machine uses. Did you use a dial indicator to properly measure the backlash to use the right figure in the backlash screen?

That looks good. Can you post a picture of your 'general logic configuration' screen and one of the motor tuning page for your x or y axis from mach3?

It's interesting as your out of shape squares could be a mixture of different things. Do you know the backlash on your machine and have you got backlash compensation set up? I am not thinking things through fully as I have to go and dow something but it could be that the rounded off edge is a consequence of the backlash from the previous corner. It doesn't look to be an issue due to leveling. Then again, backlash shouldnt give you such different results at different speed whereas CV could.

Yes Crunchy, I have flown it a few times when I have been able to get in. Like everything else, hit and miss.

You might have been able to do that in extended mode which is no longer available. I dont think it is possible anymore.

On the 'B', the cut looks ok. You say it looks like an 8 because of the rounded over corner at the top left and top bottom. You could try making a rectangle that has four square corners (obviously!) that is the same height and width of the B and see how that engraves. I dont think your cutter is the issue but a machine/software setting probably. Lets see if you get rounded off corners and which corners. It could indicate bad backlash or accelleration parameters. If you are using mach 3 you might have the constant velocity interfereing where it will round off a corner instead of making it sqaure so that the machine isnt making sudden jerky movements etc. BTW, on the second one it looks like the depth is getting greater at the bottom. This is most likely because the surface was not completely flat or your rowmark was not down flat against your surface. Secondly, perhaps your bit was not tight and moving out of the collett as you engrave but thats more likely to happen with heavy cuts. Otherwise a mechanical issue and perhaps your Z was missing steps.. Unfortunately, there are lots of possibilities..

Doesnt seem to be. I had a quick poke around the lua files and changed some HDR parameters to tone it down but didnt notice any change.

Interestingly I found that even with the vsync thing I had judder when I managed to get in to the t51 for the landing scenario. What it appears to be is the buildings when looking at somewhat dense buildings. I can literally look over to the right and its silky smooth, then I look to the left and it will start to judder as I look towards the buildings. So they seem to def be a problem. I didnt notice at first because the scenarios I first tried were at altitude.

Here is the video. Looking at teh gcode, the spindle speed is 12000 and feed is 720mm/min. Although because it is such a start stop thing, and because of the accelleration settings it might never get to that speed. Hard to know what speeds its actually going at.

Video taking ages.. Here are some photos, they were taken a long time ago, same with the video otherwise I would have done a nice one.. The text is the size it should be for the cdu buttons, to give an idea of scale. It is done in material that is used for rotary engraving. While I normally laser engrave for the cdu keys I wanted to engrave and mill out the keys in one go rather than engrave, move and set it up on the router. You can see the text looks deep, its not too bad, could be not quite as deep but more noticable in the pic.

I am just uploading a video to youtube of some rotary engraving I did for a CDU, you can see how it compares to what is going on with yours. I am not using a 60 deg vbit, that will give you awful results IMHO and you can only do stick fonts because of the sharp tip you cannot do proper pocketing without going deep to get the correct overlap for each pass. I am using an engraving bit that I think has something like Lynx's 0.02" rounded edge (actually, pic shows its a flat tip). As soon as thats uploaded I will edit the post and put some pics too. Didnt realise I cant access my pics on the phone while it is uploading..

vsync off for me or it has judder. I need to force vsync off in the nvidia control panel as unticking in game doesnt do the job. settings on high, by pressing the 'high' presets button. if @4.5, 780ti. I was getting 150fps in the rift on the su25t on the mozdok landing scenario. You must have 0.7 to run, that will run in direct mode as extended is not supported. 0.6 should not run because the game was compiled against the 0.7 SDK. Remember, oculus have tried to make each runtime compatible with the previous one - i.e. 0.7 runtime could run something compiled with 0.6 but this is different because DCS was compiled with the 0.7 SDK so could not be run with the 0.6 runtime.

Yes, brightness is way up, the dusk flight was like I was flying on a gright day with everything washed out.

No option for anything in 0.7 it's just direct. I was using the default high presets on a i5 @4.5 with 780ti. Forcing vsync off in nvidia control planel seems to be what got rid of the judder.

Once I forced vsync off in the nvidia control panel and got in the rift without it crashing it was the best flying experience in the rift I have had. It was silky smooth. I pressed ctrl-pause to see if I could see the framerate in the rift. I could and it was 150fps on the su25t evening landing scenario on high settings.

posted in the bugs thread but copied here for info... OK, I changed the Vsync in the nvidia control panel to force it off as doing in game did nothing. I also changed VR pre render frames from 1 to application controlled. I dont think this was the reason but next time I loaded DCS it all worked.. I thought I had stumbled on a solution but of course the next couple of times it crashed. Anyway, the revelation. Vsync forced off as you were saying was silky smooth. I was saying that I wanted this to be like flyinside fsx which was the best flight simming in the rift to date. DCS is better. Much better. it is silky, silky smooth. I put the frame rate counter on and I was at 150 fps in the rift. Damn, when we get the crash gone this will be nice.

OK, I changed the Vsync in the nvidia control panel to force it off as doing in game did nothing. I also changed VR pre render frames from 1 to application controlled. I dont think this was the reason but next time I loaded DCS it all worked.. I thought I had stumbled on a solution but of course the next couple of times it crashed. Anyway, the revelation. Vsync forced off as you were saying was silky smooth. I was saying that I wanted this to be like flyinside fsx which was the best flight simming in the rift to date. DCS is better. Much better. it is silky, silky smooth. I put the frame rate counter on and I was at 150 fps in the rift. Damn, when we get the crash gone this will be nice.

I am sure vsync is off by default and that I didnt turn it on, the judder is very bad. Though if you have it smooth it's nice to know that perhaps it is not an inherent issue with the implementation and case by case.

I got in once where it didnt crash. After my first flight without the rift on high settings and getting 140 FPS I had high hopes. I have to say, my first flight in the rift had as much stuttering with head movement as before. I hope that there will be an improvement there, I cant play it as it is or my stomach will start to crawl up.

Call me stupid, I would like to get the log file but I read the faq and I have no directory called 'logs', 'saved games' etc under my DCS directory. I can find it in my documents directory or any where else that I guessed it could be?