All Activity

Yes there are plenty of examples where FF might have an edge, if the particular scenario is important to you, sure, If you dive it once or twice and don't come back to it FF, APS-C or m43 will all likely produce an acceptable result. I'm not sure how particulates come into your example to favour full frame though. Low light sure particularly with a constant light source, though video lights on a wreck can only illuminate a very small proportion of it I would think.

Try shooting a wreck in low light with suspended particulate using off camera constant light sources and you'll see why a bigger sensor is a benefit.

Enjoy!!!!

An other test to be sure that it's ok Now for me it's time to leave..... it's diving day :)

Chris makes an excellent point on “I want one”. Given the costs of underwater photo gear, , Buyer’s Remorse is awful thing! If you feel you are really missing out and would be disappointed by not having FF and, as Chris says, you have the means and appreciate the downsides, then go for it! Do nt be faced with Buyer’s Remorse. Just don’t think it’ll necessarily give you significantly better images. Composition will do that - and that comes at no cost.

It works.... in consequence It was not the local Swiss-French setup of my PC (or perhaps but your change solve the problem)

You see I made a screenshot and with paste....

I don't doubt there are solid reasons for using a FF system and one of them is no doubt, I want one, I can afford it and I'm prepared for the weight and travel issues. However to fair again, shooting at f2.8 is not something everyone can do with the lenses they have and to get the best out of fisheyes behind domes and wide rectilinears requires stopping down to at least f11 for many people's tastes. For me I occasionally run into trouble with sunbursts with Olympus, often due to laziness on my part setting things up but overall I'm happy with what it puts out. I should add this applies to the latest 20MP sensors, the earlier 16MP sensors seem to me to be a step behind.

OK so a bit out of the way then. I'm likely going on Saturday, I've got a ticket so should be there.

I can see the request succeeding and the HTML arriving. The next bit is in how the browser adds that HTML to the page, and I’ve put a small fix in for that. Could you refresh the topic (Cmd/Ctrl-Shift-R) and click the empty reply box once more? If “Drag files here…” shows up, we’re done. The French Windows test can wait.

Thanks — that 20-second wait matches what we captured. The request for the attachment bar succeeded and the HTML was in the response; it just never got added to the page on your machine. Your Swiss-French Windows idea is a good test. The forum account is already set to English; what’s different is the browser reporting language Fr. If you get a chance to switch the PC (or just Edge) to English and click the empty reply box once, that would tell us whether locale is involved. No rush, and you don’t need DevTool

An idea... I'm using a PC with the language set to French... just as info... If I have time I'll switch to English and show if something change ( I had in my work life some trouble with Swiss-German language setup together with Time I need to be sure that the reason of the problem is not a "setup" problem... that is not handle in the good way. Sorry but my PC is configure as Swiss-French it is certainly a test to do to change it to English

I waited 20 seconds ?... nothing appear

One would think the story is clear but it is not :-) In short glass is glass and these are two different tools for different jobs. I am on my way to Maldives to see what the X6 is going to be about and on the meantime I am posting two lab shots. One at couple centimeters from the pad and one at like 60cm. This may not be the whole story as after Maldives I will have ocean samples from X5 in Pro and Nauticam cases and X6 in Pro case. And then we will see.

I have now captured the failure on your account twice, automatically, without you needing DevTools. Once on this topic at 17:04, and once in a private message at 19:39. Same result both times. Invision does have a client-side debug path, but it is switched off in the version they ship. When the attachment area fails to appear, the software calls Debug.error() — and in production that call goes nowhere. Debug starts disabled, nothing ever turns it on, and no adapter is registered to write those messages anywhere. The failure never reaches the server logs, which is why there was nothing useful to look at on our side. So I added a small diagnostic of our own. It watches the reply box expand, records whether the attachment request happened, what came back, and whether the "Drag files here..." bar actually appeared in the page. That is how we caught your two failures today. It does not collect the text of unsent messages — only whether the attachment UI loaded. The request that fetches the attachment area does reach the server, and the server answers 200 OK with a full response. The upload library also loads. After that, the bar never appears in the page. It isn't hidden, and it isn't being removed by an extension — it simply never gets inserted. New topics, post edits, and any reply box that already has text in it ship the attachment area with the page. A blank reply box (forum or messenger) fetches it afterwards. Only that second path is failing for you. Your account is not the problem. Two other members on Windows 11 with Chromium 151 also work. Zoom, High Contrast, and storage are all fine on the sessions we captured. Object.assign ERROR You were right to flag that, and the analysis you posted got the structure genuinely right — new topics load the editor in full, replies fetch part of it separately. That matches the source code exactly. The error itself turned out to be a dead end. I get that identical "Cannot convert undefined or null to object" message on my own machine, in a session where uploading works perfectly. It is a harmless ordering bug in the notification code, unrelated to attachments. Real, and worth chasing, and I did chase it. It just didn't lead anywhere. Could you try once more, on this topic, the same way it usually fails — click into the empty reply box and wait a few seconds. If the attachment area still doesn't appear, you don't need to paste anything from DevTools. A short "still missing" here is enough; we will already have the diagnostic. If you have a moment, a second try in a private message (empty reply box again) would be useful too. That is the other place we saw it fail. thanks...

Marelux lists the RF 20-50mm PZ on the Aquista 135D lens chart with a zoom gear (#51211) and an extension 30, so zoom range from 28mm to 50mm. I don't see the lens on the port chart yet but my guess is that the extension 30 with a 180mm dome port would be a good starting point. As a side bar, Marelux has also added the new RF 7-14mm fisheye zoom with zoom gear #51210 and extension ring 30 with the 140mm dome port with bayonet dome shade.

Welcome. I am selling a Nikon D7200, Ikelite Fourlock housing and assorted Nikon lenses if you want to purchase something to get started. Let me know. Dave

It just depends on what you shoot. For macro, I agree that high dynamic range is often not needed. But I’m primarily a shallow water wide angle shooter, and the background in those shots is natural light, where high dynamic range can make all the difference between a shot working or not. The real noise/image quality differences are greater than shown on the DXO graphs. To make a fair comparison, images need to be normalized to the same resolution. However, DXO downsizes the images to 8mp, which is very inadequate for photographers licensing their photos, making large prints, entering big contests, etc. For people like myself who want to make full use of the 60mp of the Sony A7RV, the useful comparison would be enlarging the Olympus files to 60mp for the comparison (or at least normalize both to a decent resolution in the 30-50mp range). With my FF setup, I do not have to stop down more or use a higher ISO than MFT. My wide angle can give sharp edges at f/2.8. Though if I am using optics that require stopping down more, my preference is to increase strobe power and exposure length rather than increasing ISO. Either way, I’m rarely shooting at higher ISO than I would be on MFT. Anyway, there is no one best sensor size. It varies according to the priorities of the individual. For many photographers, MFT provides adequate image quality for how they use their photos, so the size/cost advantages make it their best choice. But for other photographers, maximizing image quality/resolution is the priority, so FF is the best choice.

@RichN I know you are and other volonteer I appreciate the work you all have done That's not the problem ;) On the other side all the member writing reviews, share some DIY etc... are also volonteer we participate to the life of the site, putting some intersting stuff on it. It's like for you time we "invest" to make the site living Thanks for try to solve "my" problem.

Cut&Paste + Drag&drop it doesn't work.. it's the same probleme. If the banner appear I can paste if it's not I Ican't paste. Why I use Paste : Easy, I use Greenshot and when I select a region I configure Greeshot to put it in the clipboard... It's fast and that's a important point for me.

Aloha and welcome Alexey! Just a thought: full frame camera and lenses are great, but if you’re planning to travel, you might consider smaller sensor cameras as the lenses (and ports) are oftentimes much smaller. Unless you really need the large file sizes, you might find that APS-c or M43 will suit your needs. More to think about, yes, but we are here to help you spend your money. Best, Craig