# CsoundUnity Win64

**URL:** <https://forum.cabbageaudio.com/t/csoundunity-win64/1906>\
**Category:** Csound for Games\
**Created:** [1 May 2020 09:30 UTC](https://forum.cabbageaudio.com/t/csoundunity-win64/1906 "2020-05-01T09:30:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [1 May 2020 09:30 UTC](https://forum.cabbageaudio.com/t/csoundunity-win64/1906/1 "2020-05-01T09:30:14Z")

</div>

Hi @giovannibedetti, I’m just starting a new thread here regarding the following posts:

[https://forum-next.cabbageaudio.com/t/csoundunity-beginner-questions/1903/23](https://forum-next.cabbageaudio.com/t/csoundunity-beginner-questions/1903/23)  
[https://forum-next.cabbageaudio.com/t/csoundunity-beginner-questions/1903/24](https://forum-next.cabbageaudio.com/t/csoundunity-beginner-questions/1903/24)  
[https://forum-next.cabbageaudio.com/t/csoundunity-beginner-questions/1903/25](https://forum-next.cabbageaudio.com/t/csoundunity-beginner-questions/1903/25)

On my Windows 10 machine this fix works fine. I can access the `date` opcodes, but continue to have issues with `exciter`. From the Csound command line we can run -z to show all opcodes that have been loaded. It would be useful to be able to this here too.

In which case I think that we should probably create an interface to [`csoundNewOpcodeList()`](https://csound.com/docs/api/group___o_p_c_o_d_e_s.html#ga678c47c3398928769b1284803ce2d0c4) so that we can see what opcodes Csound is actually adding to its `opcodeListEntry`.

I think this one is above my level of C# skills! I can just about get my head around marshalling straight-up pointers, but this one also requires us to work with C structures?

FWIW I’m learning a lot of C# from studying your code!

---

<div class="post-metadata">

**Author:** ![giovannibedetti](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/giovannibedetti/32/4146_2.png) [@giovannibedetti](https://forum.cabbageaudio.com/u/giovannibedetti)\
**Post date:** [1 May 2020 10:05 UTC](https://forum.cabbageaudio.com/t/csoundunity-win64/1906/2 "2020-05-01T10:05:05Z")

</div>

> [@rorywalsh](#):
>
> In which case I think that we should probably create an interface to [`csoundNewOpcodeList()`](https://csound.com/docs/api/group___o_p_c_o_d_e_s.html#ga678c47c3398928769b1284803ce2d0c4) so that we can see what opcodes Csound is actually adding to its `opcodeListEntry` .

Ok I’ll look into it!  
BTW I’m also learning a lot, so thank you! 💪