First thing - you do have the path set correctly in the exporter's main dialog to the Octane binary exe on your PC, and to other folders etc as listed [you should get error messages if not anyway] ?
Please ensure that the file-paths for the project do not contain non-standard characters - e.g. unicode accented letters - these can fail in PC based SUP-Ruby...
Also please check that you have appropriate access rights to read/write/open files etc in the project folder and the other folders that will be listed later...
Let's assume that none of this is the problem...
Is your MAC version working OK?
On your Windows machine please find your temp folder by opening the Ruby Console and typing/copy+paste ENV["TEMP"]
- typically returns something like 'C:\Users\Tim\AppData\Local\Temp'.
Open that folder because we'll need to look in it later [it might be 'hidden' - switch on view-hidden files in your folder-options - also viewing all file-extensions could be useful during this test as there are a lot of files with the same name, but different suffixes].
Also open 'C:\Temp' [if it doesn't exist please make it!] and the Project's folder [all three in separate windows].
Leave the Ruby Console window open to see any error messages,...
Run the exporter tool and the main dialog opens.
Enter a new project name so that we get a fresh set of OBJ files etc - say 'xxx'...
The project folder can stay as it is.
Click on 'OBJ/MTL only' button.
Does it make the new xxx.OBJ/xxx.MTL files and a 'xxx_Textures' folder in the Project's folder?
Any Ruby Console errors?
Now click on 'Render Frame' button.
It should make the xxx.OBJ/xxx.MTL etc as before [it always makes a fresh set] - does it ?
Any Ruby Console errors?
It also should make a 'start.cmd' file in the TEMP folder with an 'octane.cmd' file which in turn it will run.
The 'start.cmd' file only appears briefly in the TEMP folder and then it self-destructs.
The 'octane.cmd' file will eventually self-destruct... BUT only when you close the main dialog [or close SUp which will of course close the dialog].
So please leave SUp running and leave the main dialog open too so we can find this cmd file to review it.
If the cmd files don't appear in your TEMP folder then look in C:\Temp\ and then in the project's folder for them in case there's a write-access problem - when it uses alternative venues...
The 'octane.cmd' file should run and make the Octane 'xxx.ocs' file in the project's folder.
Assuming that the 'xxx.ocs' exists but it hasn't automatically opened in Octane can you open it by double-clicking its icon?
If so is it as expected - contents/view/materials etc?
If not what errors appeared?
Back to the cmd file - let's assume the 'octane.cmd' file exists.
If the 'xxx.ocs' file was not there what a happens when you double-click the 'octane.cmd' file icon?
It should make the 'xxx.ocs' file in the project folder and then open it with Octane ?
If not then please Edit the 'octane.cmd' file in a text-editor [e.g. NotePad.exe] [Note: not 'Open' as that is =='Run'], and read the contents...
Do they seem to have the correct/expected file-paths and arguments/functions listed ?
I appreciate that it might look a bit gobbledygook-ish to a layman but there is a logic to what it contains...
If you have the text from that file please can you copy/paste it into a post so we can see what the file says exactly...
If all seems well and it's still not working please check that 'cmd' files are correctly setup o your PC.
On the start menu pick 'Run...' and type cmd
- did a command window open? [C:\Windows\system32\cmd.exe]
The reason for this failure could be one of many thing... by going through the list above we should find it - it might even be completely unconnected to the tool itself, but something with your system setup that needs tweaking... We will sort this together