Page 2 of 2
Re: Driver San Francisco PC ???
Posted: Tue Jan 04, 2022 6:30 pm
by Durik256
shakotay2 wrote: ↑Tue Jan 04, 2022 8:31 am
the data is corrupted:
maybe the data is corrupted
but i can't load empty model (NoeModel()) from button click.
Code: Select all
def ButtonClick(noeWnd, controlId, wParam, lParam, mdlList):
mdlList.append(NoeModel())#dont work
return True
I tried through rapi.toolLoadGData(mList)
Code: Select all
mList = [NoeModel(),NoeModel(),NoeModel()...]
rapi.toolLoadGData(mList)
I get an error "
RuntimeError: Called rapi function in uninitialized state!"
Re: Driver San Francisco PC ???
Posted: Tue Jan 04, 2022 6:45 pm
by shakotay2
I'll have a look at it asap! Your using very interesting ("windows") features from Noesis, btw.
So there's not many .py scrips as a reference. In fact I don't have any other samples which (for example) use
getControlById (from noewin.py).
You're (one of) the first to use it, congratz.
Reason is that most scripts deal with seperate model files only, not with an archiv.
Re: Driver San Francisco PC ???
Posted: Tue Jan 04, 2022 7:01 pm
by Durik256
shakotay2 wrote: ↑Tue Jan 04, 2022 6:45 pm
congratz.
thank
I solved the "load Selected" issue. saving to a temporary file and opening it.
Code: Select all
exportVEHC(listIndex)
noesis.openAndRemoveTempFile(tempPath)
But I still want to load the model into the previewer via the toolbar without opening the file

Re: Driver San Francisco PC ???
Posted: Tue Jan 04, 2022 7:34 pm
by shakotay2
Durik256 wrote: ↑Tue Jan 04, 2022 7:01 pmBut I still want to load the model into the previewer via the toolbar without opening the file

I know.

You'd need a debugger for such to find the cause of the problem. (Checking object addresses using the integrated "Universal debugger", from Noesis/Tools gave me no clues.)
edit: I logged some offsets:
thinking...
(they had to be different because they were from a specific .VEHC versa it's corresponding data block in the .sp)
Search for string "Pooled vertex dependencies>>>" in .VEHC file. After that the mentioned offsets start.
This is totally strange, I logged vertices and face indices into a file when using "Load selected" and this is the result (why the heck doesn't noesis display the model then?

)
.
strange_ok.png
Re: Driver San Francisco PC ???
Posted: Wed Jan 05, 2022 3:15 am
by Durik256
shakotay2 wrote: ↑Tue Jan 04, 2022 7:34 pm
This is totally strange, I logged vertices and face indices into a file when using "Load selected" and this is the result (why the heck doesn't noesis display the model then?

)
it loads the models only once the first time the method is called "noesis.setHandlerLoadModel(handle, noepyLoadModel)" when we open registered file.
works here:
Durik256 wrote: ↑Tue Jan 04, 2022 7:01 pm
saving to a temporary file and opening it.
I think we've had enough, let the author of this topic figure it out

Re: Driver San Francisco PC ???
Posted: Wed Jan 05, 2022 7:08 pm
by Durik256
new .sp file extractor

Re: Driver San Francisco PC ???
Posted: Wed Jan 05, 2022 8:02 pm
by shakotay2
Very quick .sp unpacking!
(And some day

we will know why it takes so long between
noepyCheckType(data) and "Detected file type: driver sf file" when loading one VEHC file (about 1 MB). Maybe that message is in the windows queue earlier, I dunno.

)
Re: Driver San Francisco PC ???
Posted: Sun Jan 09, 2022 10:23 pm
by ReVolt
this is cool...but the wheels are not positioned and no textures.

Re: Driver San Francisco PC ???
Posted: Mon Jan 10, 2022 12:54 am
by ReVolt
I got textures using DragonUnPACKer but I have an issue
some of the textures are wrong color
How do I fix this?
Re: Driver San Francisco PC ???
Posted: Mon Jan 10, 2022 1:11 am
by ReVolt
AHA, the trick was...these textures weren't even supposed to have color! I grayscaled them and it looks correct now.
for the wheels I just seperated the brake models from the model, set origin on them, and positioned the wheels from there.
